CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-70188 |
critical
|
9.1 |
0.0094
|
Microsoft |
ASP.NET Core 11.0 |
11.0
< 11.0.0-rc.2
|
|
CVE-2026-70188 |
critical
|
9.1 |
0.0094
|
Microsoft |
ASP.NET Core 8.0 |
8.0
< 8.0.32
|
|
CVE-2026-70188 |
critical
|
9.1 |
0.0094
|
Microsoft |
ASP.NET Core 9.0 |
9.0
< 9.0.21
|
|
CVE-2026-70188 |
critical
|
9.1 |
0.0094
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.42
|
|
CVE-2026-70188 |
critical
|
9.1 |
0.0094
|
Microsoft |
Microsoft Visual Studio 2026 version 18.10 |
18.10.0
< 18.10.4
|
|
CVE-2026-62916 |
critical
|
9.1 |
0.0086
|
Microsoft |
Microsoft Entra |
-
|
|
CVE-2026-69641 |
critical
|
9.1 |
0.0086
|
Microsoft |
Microsoft Exchange Server 2016 Cumulative Update 23 |
15.01.0.0
< 15.01.2507.073
|
|
CVE-2026-69641 |
critical
|
9.1 |
0.0086
|
Microsoft |
Microsoft Exchange Server 2019 Cumulative Update 14 |
15.02.0.0
< 15.02.1544.046
|
|
CVE-2026-69641 |
critical
|
9.1 |
0.0086
|
Microsoft |
Microsoft Exchange Server 2019 Cumulative Update 15 |
15.02.0.0
< 15.02.1748.051
|
|
CVE-2026-69641 |
critical
|
9.1 |
0.0086
|
Microsoft |
Microsoft Exchange Server Subscription Edition RTM |
15.02.0.0
< 15.02.2562.049
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
microsoft |
windows_10_1607 |
< 10.0.14393.9612
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
microsoft |
windows_10_1809 |
< 10.0.17763.9376
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
microsoft |
windows_10_21h2 |
< 10.0.19044.7807
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
microsoft |
windows_10_22h2 |
< 10.0.19045.7807
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
microsoft |
windows_11_23h2 |
< 10.0.22631.7652
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
microsoft |
windows_11_24h2 |
< 10.0.26100.9711
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
microsoft |
windows_11_25h2 |
< 10.0.26200.9711
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
microsoft |
windows_11_26h1 |
< 10.0.28000.3231
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
microsoft |
windows_11_26h2 |
< 10.0.26300.9711
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
microsoft |
windows_server_2012 |
-
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
microsoft |
windows_server_2012 |
r2
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
microsoft |
windows_server_2022 |
< 10.0.20348.5761
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-58289 |
critical
|
9.0 |
0.0199
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows 10 Version 1607 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-85818 |
critical
|
9.0 |
0.0041
|
Microsoft |
Windows 11 version 23H2 |
10.0.22631.0
< 10.0.22631.7652
|
|
CVE-2026-26149 |
critical
|
9.0 |
0.0056
|
microsoft |
power_apps |
< 3.26032.10.0
|
|
CVE-2026-33844 |
critical
|
9.0 |
0.0099
|
microsoft |
azure_managed_instance_for_apache_cassandra |
-
|
|
CVE-2026-58289 |
critical
|
9.0 |
0.0199
|
microsoft |
edge_chromium |
< 150.0.4078.48
|
|
CVE-2026-77903 |
critical
|
9.0 |
0.0037
|
microsoft |
dataverse |
-
|
|
CVE-2026-85818 |
critical
|
9.0 |
0.0041
|
microsoft |
windows_11_23h2 |
< 10.0.22631.7652
|
|
CVE-2026-85818 |
critical
|
9.0 |
0.0041
|
microsoft |
windows_11_24h2 |
< 10.0.26100.9711
|
|
CVE-2026-85818 |
critical
|
9.0 |
0.0041
|
microsoft |
windows_11_25h2 |
< 10.0.26200.9711
|
|
CVE-2026-85818 |
critical
|
9.0 |
0.0041
|
microsoft |
windows_11_26h1 |
< 10.0.28000.3231
|
|
CVE-2026-85818 |
critical
|
9.0 |
0.0041
|
microsoft |
windows_11_26h2 |
< 10.0.26300.9711
|
|
CVE-2026-85818 |
critical
|
9.0 |
0.0041
|
microsoft |
windows_server_2022 |
< 10.0.20348.5761
|
|
CVE-2026-85818 |
critical
|
9.0 |
0.0041
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows 10 Version 1809 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows 10 Version 21H2 |
10.0.19044.0
< 10.0.19044.7807
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows 10 Version 22H2 |
10.0.19045.0
< 10.0.19045.7807
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows 11 version 23H2 |
10.0.22631.0
< 10.0.22631.7652
|
|