CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26434
|
|
CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23470
|
|
CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23470
|
|
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-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_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-61223 |
critical
|
9.0 |
0.0039
|
oracle |
communications_converged_application_server |
8.2.0
|
|
CVE-2026-61223 |
critical
|
9.0 |
0.0039
|
oracle |
communications_converged_application_server |
8.3.0
|
|
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-90865 |
critical
|
9.0 |
0.0114
|
Progress Software |
WS_FTP Server |
0
< 2024.0.7
|
|
CVE-2026-90865 |
critical
|
9.0 |
0.0114
|
Progress Software |
WS_FTP Server |
0
< 2025.0.4
|
|
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 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-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
|
|