CVE-2026-71336 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72986 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72986 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-77495 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-77495 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-77504 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-77504 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-83996 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-83996 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-83998 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-83998 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69499 |
high
|
8.8 |
0.0082
|
microsoft |
windows_server_2019 |
< 10.0.17763.9245
|
|
CVE-2026-73013 |
high
|
8.8 |
0.0082
|
microsoft |
windows_server_2019 |
< 10.0.17763.9245
|
|
CVE-2026-27928 |
high
|
8.7 |
0.0041
|
microsoft |
windows_server_2019 |
< 10.0.17763.8644
|
|
CVE-2026-32162 |
high
|
8.4 |
0.0192
|
microsoft |
windows_server_2019 |
< 10.0.17763.8644
|
|
CVE-2026-49184 |
high
|
8.4 |
0.0034
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|
CVE-2026-54122 |
high
|
8.4 |
0.0036
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|
CVE-2026-54992 |
high
|
8.4 |
0.0034
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
1 PoC
|
CVE-2026-54128 |
high
|
8.4 |
0.0036
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|
CVE-2026-69479 |
high
|
8.4 |
0.0036
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69479 |
high
|
8.4 |
0.0036
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69638 |
high
|
8.4 |
0.0036
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69638 |
high
|
8.4 |
0.0036
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-77503 |
high
|
8.4 |
0.0034
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-77503 |
high
|
8.4 |
0.0034
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-50429 |
high
|
8.2 |
0.0107
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|
CVE-2026-50680 |
high
|
8.2 |
0.0034
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|
CVE-2026-69874 |
high
|
8.2 |
0.0029
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69874 |
high
|
8.2 |
0.0029
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69906 |
high
|
8.2 |
0.0035
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69906 |
high
|
8.2 |
0.0035
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72961 |
high
|
8.2 |
0.0035
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72961 |
high
|
8.2 |
0.0035
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-81354 |
high
|
8.2 |
0.0035
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-81354 |
high
|
8.2 |
0.0035
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69846 |
high
|
8.2 |
0.0035
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69846 |
high
|
8.2 |
0.0035
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72962 |
high
|
8.2 |
0.0035
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72962 |
high
|
8.2 |
0.0035
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69802 |
high
|
8.1 |
0.0063
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-70062 |
high
|
8.1 |
0.0077
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-70229 |
high
|
8.1 |
0.0104
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-88117 |
high
|
8.1 |
0.0070
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-88119 |
high
|
8.1 |
0.0076
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-88120 |
high
|
8.1 |
0.0076
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-42900 |
high
|
8.1 |
0.0054
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|
CVE-2026-49164 |
high
|
8.1 |
0.0079
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|
CVE-2026-50694 |
high
|
8.1 |
0.0079
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|
CVE-2026-54995 |
high
|
8.1 |
0.0079
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|
CVE-2026-50439 |
high
|
8.1 |
0.0079
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|