CVE-2026-83983 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-83983 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-83985 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-83985 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-83987 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-83987 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-83995 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-83995 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-84000 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-84000 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-56172 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-56172 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-56177 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-56177 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-62810 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-62810 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68832 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68832 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68841 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68841 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68844 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68844 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68845 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68845 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68848 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68848 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68877 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68877 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68885 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68885 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68888 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68888 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68890 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68890 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68892 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68892 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69269 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69269 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69270 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69270 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69277 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69277 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69289 |
high
|
7.8 |
0.0037
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69289 |
high
|
7.8 |
0.0037
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69293 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69293 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69295 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69295 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69307 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69307 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|