CVE-2026-49798 |
critical
|
9.3 |
0.0036
|
microsoft |
windows_10_21h2 |
< 10.0.19044.7548
|
|
CVE-2026-49798 |
critical
|
9.3 |
0.0036
|
microsoft |
windows_10_22h2 |
< 10.0.19045.7548
|
|
CVE-2026-49798 |
critical
|
9.3 |
0.0036
|
microsoft |
windows_11_24h2 |
< 10.0.26100.8875
|
|
CVE-2026-49798 |
critical
|
9.3 |
0.0036
|
microsoft |
windows_11_25h2 |
< 10.0.26200.8875
|
|
CVE-2026-49798 |
critical
|
9.3 |
0.0036
|
microsoft |
windows_11_26h1 |
< 10.0.28000.2269
|
|
CVE-2026-49798 |
critical
|
9.3 |
0.0036
|
microsoft |
windows_11_26h1 |
< 10.0.28000.2525
|
|
CVE-2026-49798 |
critical
|
9.3 |
0.0036
|
microsoft |
windows_server_2012 |
-
|
|
CVE-2026-49798 |
critical
|
9.3 |
0.0036
|
microsoft |
windows_server_2012 |
r2
|
|
CVE-2026-49798 |
critical
|
9.3 |
0.0036
|
microsoft |
windows_server_2016 |
< 10.0.14393.9339
|
|
CVE-2026-49798 |
critical
|
9.3 |
0.0036
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|
CVE-2026-49798 |
critical
|
9.3 |
0.0036
|
microsoft |
windows_server_2022 |
< 10.0.20348.5386
|
|
CVE-2026-49798 |
critical
|
9.3 |
0.0036
|
microsoft |
windows_server_2025 |
< 10.0.26100.33158
|
|
CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
Microsoft |
Windows 10 Version 1607 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2025-13590 |
critical
|
9.1 |
0.0077
|
WSO2 |
WSO2 API Manager |
4.2.0
< 4.2.0.179
|
|
CVE-2026-44542 |
critical
|
9.1 |
0.0052
|
gtsteffaniak |
filebrowser_quantum |
< 1.3.1
|
|
CVE-2026-44542 |
critical
|
9.1 |
0.0052
|
gtsteffaniak |
filebrowser_quantum |
< 1.3.9
|
|
CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
microsoft |
windows_10_1607 |
< 10.0.14393.9612
|
|
CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
microsoft |
windows_10_1809 |
< 10.0.17763.9376
|
|
CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
microsoft |
windows_server_2012 |
-
|
|
CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
microsoft |
windows_server_2012 |
r2
|
|
CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
microsoft |
windows_server_2022 |
< 10.0.20348.5761
|
|
CVE-2026-96252 |
critical
|
9.1 |
0.0056
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-90866 |
critical
|
9.1 |
0.0073
|
Progress Software |
WS_FTP Server |
0
< 2024.0.7
|
|
CVE-2026-90863 |
critical
|
9.1 |
0.0066
|
Progress Software |
WS_FTP Server |
0
< 2024.0.7
|
|
CVE-2026-90864 |
critical
|
9.1 |
0.0048
|
Progress Software |
WS_FTP Server |
0
< 2024.0.7
|
|
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 10 Version 1809 |
10.0.17763.0
< 10.0.17763.9376
|
|
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_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
|
|