CVE-2026-72960 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-73006 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-73006 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-73012 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-73012 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-73013 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
-
|
|
CVE-2026-73013 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
-
|
|
CVE-2026-73018 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-73018 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-73023 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-73023 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-80096 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-80096 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-81955 |
high
|
8.8 |
0.0084
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-81955 |
high
|
8.8 |
0.0084
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-83992 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-83992 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-62706 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-62706 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68828 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68828 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69266 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69266 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69461 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69461 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69485 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69485 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69494 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69494 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69495 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69495 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69518 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69518 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69551 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69551 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69603 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69603 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69628 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69628 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69676 |
high
|
8.8 |
0.0078
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69676 |
high
|
8.8 |
0.0078
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69712 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69712 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69772 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69772 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69860 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69860 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-70586 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-70586 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-71336 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|