CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows 11 Version 23H2 |
10.0.22631.0
< 10.0.22631.7652
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows 11 Version 24H2 |
10.0.26100.0
< 10.0.26100.9711
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows 11 Version 25H2 |
10.0.26200.0
< 10.0.26200.9711
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows 11 version 26H1 |
10.0.28000.0
< 10.0.28000.3231
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows 11 Version 26H2 |
10.0.26300.0
< 10.0.26300.9711
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26434
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26434
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23470
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23470
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-105008 |
critical
|
9.0 |
0.0066
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-85818 |
critical
|
9.0 |
0.0041
|
Microsoft |
Windows 11 Version 23H2 |
10.0.22631.0
< 10.0.22631.7652
|
|
CVE-2026-85818 |
critical
|
9.0 |
0.0041
|
Microsoft |
Windows 11 Version 24H2 |
10.0.26100.0
< 10.0.26100.9711
|
|
CVE-2026-85818 |
critical
|
9.0 |
0.0041
|
Microsoft |
Windows 11 Version 25H2 |
10.0.26200.0
< 10.0.26200.9711
|
|
CVE-2026-85818 |
critical
|
9.0 |
0.0041
|
Microsoft |
Windows 11 version 26H1 |
10.0.28000.0
< 10.0.28000.3231
|
|
CVE-2026-85818 |
critical
|
9.0 |
0.0041
|
Microsoft |
Windows 11 Version 26H2 |
10.0.26300.0
< 10.0.26300.9711
|
|
CVE-2026-85818 |
critical
|
9.0 |
0.0041
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-85818 |
critical
|
9.0 |
0.0041
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-85818 |
critical
|
9.0 |
0.0041
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-69854 |
critical
|
9.0 |
0.0069
|
Microsoft |
Spring Cloud Azure |
1.0.0
< 7.4.0
|
|
CVE-2026-67378 |
critical
|
9.0 |
0.0071
|
Microsoft |
Microsoft SQL Server 2019 (CU 32) |
15.0.0.0
< 15.0.4490.9
|
|
CVE-2026-67378 |
critical
|
9.0 |
0.0071
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2190.7
|
|
CVE-2026-67378 |
critical
|
9.0 |
0.0071
|
Microsoft |
Microsoft SQL Server 2022 (CU 26) |
16.0.0.0
< 16.0.4275.2
|
|
CVE-2026-67378 |
critical
|
9.0 |
0.0071
|
Microsoft |
Microsoft SQL Server 2022 (GDR) |
16.0.0
< 16.0.1200.5
|
|
CVE-2026-67378 |
critical
|
9.0 |
0.0071
|
Microsoft |
Microsoft SQL Server 2025 (CU8) |
17.0.0.0
< 17.0.4085.5
|
|
CVE-2026-67378 |
critical
|
9.0 |
0.0071
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1135.8
|
|
CVE-2026-67636 |
critical
|
9.0 |
0.0071
|
Microsoft |
Microsoft SQL Server 2019 (CU 32) |
15.0.0.0
< 15.0.4490.9
|
|
CVE-2026-67636 |
critical
|
9.0 |
0.0071
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2190.7
|
|
CVE-2026-67636 |
critical
|
9.0 |
0.0071
|
Microsoft |
Microsoft SQL Server 2022 (CU 26) |
16.0.0.0
< 16.0.4275.2
|
|
CVE-2026-67636 |
critical
|
9.0 |
0.0071
|
Microsoft |
Microsoft SQL Server 2022 (GDR) |
16.0.0
< 16.0.1200.5
|
|
CVE-2026-67636 |
critical
|
9.0 |
0.0071
|
Microsoft |
Microsoft SQL Server 2025 (CU8) |
17.0.0.0
< 17.0.4085.5
|
|
CVE-2026-67636 |
critical
|
9.0 |
0.0071
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1135.8
|
|
CVE-2026-77903 |
critical
|
9.0 |
0.0037
|
Microsoft |
Microsoft Dataverse |
-
|
|
CVE-2026-47300 |
high
|
8.8 |
0.0078
|
microsoft |
.net |
< 8.0.29
|
|
CVE-2026-47300 |
high
|
8.8 |
0.0078
|
microsoft |
visual_studio_2022 |
< 17.12.22
|
|
CVE-2026-47300 |
high
|
8.8 |
0.0078
|
microsoft |
visual_studio_2026 |
< 18.7.4
|
|
CVE-2026-47303 |
high
|
8.8 |
0.0084
|
microsoft |
.net |
< 8.0.29
|
|
CVE-2026-47303 |
high
|
8.8 |
0.0084
|
microsoft |
visual_studio_2022 |
< 17.12.22
|
|
CVE-2026-47303 |
high
|
8.8 |
0.0084
|
microsoft |
visual_studio_2026 |
< 18.7.4
|
|
CVE-2026-103575 |
high
|
8.8 |
0.0085
|
microsoft |
windows_10_1607 |
< 10.0.14393.9612
|
|
CVE-2026-103575 |
high
|
8.8 |
0.0085
|
microsoft |
windows_10_1809 |
< 10.0.17763.9376
|
|
CVE-2026-103575 |
high
|
8.8 |
0.0085
|
microsoft |
windows_10_21h2 |
< 10.0.19044.7807
|
|
CVE-2026-103575 |
high
|
8.8 |
0.0085
|
microsoft |
windows_10_22h2 |
< 10.0.19045.7807
|
|
CVE-2026-103575 |
high
|
8.8 |
0.0085
|
microsoft |
windows_11_23h2 |
< 10.0.22631.7652
|
|
CVE-2026-103575 |
high
|
8.8 |
0.0085
|
microsoft |
windows_11_24h2 |
< 10.0.26100.9711
|
|