CVE-2026-87302 |
critical
|
9.1 |
0.0042
|
Oracle Corporation |
Oracle WebLogic Server |
14.1.2.0.0
|
|
CVE-2026-87302 |
critical
|
9.1 |
0.0042
|
Oracle Corporation |
Oracle WebLogic Server |
15.1.1.0.0
|
|
CVE-2026-90863 |
critical
|
9.1 |
0.0066
|
Progress Software |
WS_FTP Server |
0
< 2025.0.4
|
|
CVE-2026-90864 |
critical
|
9.1 |
0.0048
|
Progress Software |
WS_FTP Server |
0
< 2025.0.4
|
|
CVE-2026-90866 |
critical
|
9.1 |
0.0073
|
Progress Software |
WS_FTP Server |
0
< 2025.0.4
|
|
CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26434
|
|
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-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-5921 |
high
|
8.9 |
0.0042
|
github |
enterprise_server |
< 3.14.26
|
|
CVE-2026-5921 |
high
|
8.9 |
0.0042
|
github |
enterprise_server |
3.20.0
|
|
CVE-2026-43639 |
high
|
8.9 |
0.0060
|
bitwarden |
server |
< 2026.4.0
|
|
CVE-2026-103575 |
high
|
8.8 |
0.0085
|
microsoft |
windows_server_2012 |
-
|
|
CVE-2026-103575 |
high
|
8.8 |
0.0085
|
microsoft |
windows_server_2012 |
r2
|
|
CVE-2026-103575 |
high
|
8.8 |
0.0085
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-103575 |
high
|
8.8 |
0.0085
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-103575 |
high
|
8.8 |
0.0085
|
microsoft |
windows_server_2022 |
< 10.0.20348.5761
|
|