CVE-2026-85339 |
high
|
8.8 |
0.0054
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85817 |
high
|
8.8 |
0.0072
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85817 |
high
|
8.8 |
0.0072
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85903 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85903 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85905 |
high
|
8.8 |
0.0035
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85905 |
high
|
8.8 |
0.0035
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85931 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85931 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85936 |
high
|
8.8 |
0.0054
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85936 |
high
|
8.8 |
0.0054
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88115 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88115 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88136 |
high
|
8.8 |
0.0095
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88136 |
high
|
8.8 |
0.0095
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88157 |
high
|
8.8 |
0.0052
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88157 |
high
|
8.8 |
0.0052
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88159 |
high
|
8.8 |
0.0142
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88159 |
high
|
8.8 |
0.0142
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88165 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88165 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-69291 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69291 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69334 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69334 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69386 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69386 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69434 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69434 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69511 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69511 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69547 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69547 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69598 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69598 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69601 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69601 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69669 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69669 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-70203 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-70203 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-71352 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-71352 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72933 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72933 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72950 |
high
|
8.8 |
0.0092
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72950 |
high
|
8.8 |
0.0092
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72959 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72959 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72960 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|