CVE-2026-65786 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-65787 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-65787 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-65790 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-65790 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-65814 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-65814 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-66799 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-66799 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-70345 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-70345 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-70346 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-70346 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-70347 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-70347 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-56174 |
high
|
7.8 |
0.0046
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-56174 |
high
|
7.8 |
0.0046
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-103577 |
high
|
7.5 |
0.0057
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-69577 |
high
|
7.5 |
0.0107
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-69789 |
high
|
7.5 |
0.0046
|
microsoft |
windows_server_2025 |
< 10.0.26100.33438
|
|
CVE-2026-69986 |
high
|
7.5 |
0.0063
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-69987 |
high
|
7.5 |
0.0063
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-69988 |
high
|
7.5 |
0.0063
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-70006 |
high
|
7.5 |
0.0063
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-70058 |
high
|
7.5 |
0.0133
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-70133 |
high
|
7.5 |
0.0127
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-70163 |
high
|
7.5 |
0.0123
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-70207 |
high
|
7.5 |
0.0075
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-83795 |
high
|
7.5 |
0.0127
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-83843 |
high
|
7.5 |
0.0127
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-85353 |
high
|
7.5 |
0.0098
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-96861 |
high
|
7.5 |
0.0112
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-96866 |
high
|
7.5 |
0.0112
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-26154 |
high
|
7.5 |
0.0106
|
microsoft |
windows_server_2025 |
< 10.0.26100.32690
|
|
CVE-2026-32071 |
high
|
7.5 |
0.0106
|
microsoft |
windows_server_2025 |
< 10.0.26100.32690
|
|
CVE-2026-40378 |
high
|
7.5 |
0.0117
|
microsoft |
windows_server_2025 |
< 10.0.26100.33158
|
|
CVE-2026-49171 |
high
|
7.5 |
0.0030
|
microsoft |
windows_server_2025 |
< 10.0.26100.33158
|
|
CVE-2026-49181 |
high
|
7.5 |
0.0117
|
microsoft |
windows_server_2025 |
< 10.0.26100.33158
|
|
CVE-2026-49787 |
high
|
7.5 |
0.0117
|
microsoft |
windows_server_2025 |
< 10.0.26100.33158
|
|
CVE-2026-49788 |
high
|
7.5 |
0.0117
|
microsoft |
windows_server_2025 |
< 10.0.26100.33158
|
|
CVE-2026-50695 |
high
|
7.5 |
0.0117
|
microsoft |
windows_server_2025 |
< 10.0.26100.33158
|
|
CVE-2026-50696 |
high
|
7.5 |
0.0117
|
microsoft |
windows_server_2025 |
< 10.0.26100.33158
|
|
CVE-2026-54119 |
high
|
7.5 |
0.0117
|
microsoft |
windows_server_2025 |
< 10.0.26100.33158
|
|
CVE-2026-54983 |
high
|
7.5 |
0.0117
|
microsoft |
windows_server_2025 |
< 10.0.26100.33158
|
|
CVE-2026-50304 |
high
|
7.5 |
0.0117
|
microsoft |
windows_server_2025 |
< 10.0.26100.33158
|
|
CVE-2026-50328 |
high
|
7.5 |
0.0123
|
microsoft |
windows_server_2025 |
< 10.0.26100.33158
|
|
CVE-2026-50330 |
high
|
7.5 |
0.0125
|
microsoft |
windows_server_2025 |
< 10.0.26100.33158
|
|
CVE-2026-50355 |
high
|
7.5 |
0.0117
|
microsoft |
windows_server_2025 |
< 10.0.26100.33158
|
|
CVE-2026-50368 |
high
|
7.5 |
0.0117
|
microsoft |
windows_server_2025 |
< 10.0.26100.33158
|
|
CVE-2026-50411 |
high
|
7.5 |
0.0117
|
microsoft |
windows_server_2025 |
< 10.0.26100.33158
|
|