CVE-2026-60699 |
high
|
8.6 |
0.0041
|
oracle |
weblogic_server |
14.1.1.0.0
|
|
CVE-2026-60699 |
high
|
8.6 |
0.0041
|
oracle |
weblogic_server |
14.1.2.0.0
|
|
CVE-2026-60699 |
high
|
8.6 |
0.0041
|
oracle |
weblogic_server |
15.1.1.0.0
|
|
CVE-2026-67625 |
high
|
8.5 |
0.0056
|
Microsoft |
Microsoft SQL Server 2017 (GDR) |
14.0.0
< 14.0.2140.2
|
|
CVE-2026-68883 |
high
|
8.5 |
0.0056
|
Microsoft |
Microsoft SQL Server 2017 (GDR) |
14.0.0
< 14.0.2140.2
|
|
CVE-2026-85886 |
high
|
8.5 |
0.0040
|
Microsoft |
Microsoft SQL Server 2017 (GDR) |
14.0.0
< 14.0.2140.2
|
|
CVE-2026-93517 |
high
|
8.5 |
0.0019
|
x.orgg |
xorg-x11-server |
0
< 21.1.25
|
|
CVE-2026-50340 |
high
|
8.5 |
0.0074
|
microsoft |
windows_server_2025 |
< 10.0.26100.33158
|
|
CVE-2026-11536 |
high
|
8.5 |
0.0058
|
ibm |
websphere_application_server |
< 8.5.5.29
|
|
CVE-2026-9203 |
high
|
8.5 |
0.0034
|
progress |
marklogic_server |
< 11.3.6
|
|
CVE-2026-71062 |
high
|
8.5 |
0.0033
|
oracle |
database_server |
< 23.26.3
|
|
CVE-2026-67625 |
high
|
8.5 |
0.0056
|
Microsoft |
Microsoft SQL Server 2017 for x64-based Systems (CU31) |
14.0.3006.16
< 14.0.3560.2
|
|
CVE-2026-67625 |
high
|
8.5 |
0.0056
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2200.2
|
|
CVE-2026-67625 |
high
|
8.5 |
0.0056
|
Microsoft |
Microsoft SQL Server 2019 for x64-based Systems (CU32) |
15.0.4003.23
< 15.0.4500.2
|
|
CVE-2026-67625 |
high
|
8.5 |
0.0056
|
Microsoft |
Microsoft SQL Server 2022 (GDR) |
16.0.0
< 16.0.1210.3
|
|
CVE-2026-67625 |
high
|
8.5 |
0.0056
|
Microsoft |
Microsoft SQL Server 2022 for x64-based Systems (CU27) |
16.0.4003.1
< 16.0.4305.5
|
|
CVE-2026-67625 |
high
|
8.5 |
0.0056
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (CU9) |
17.0.4006.2
< 17.0.5015.4
|
|
CVE-2026-67625 |
high
|
8.5 |
0.0056
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1145.4
|
|
CVE-2026-68883 |
high
|
8.5 |
0.0056
|
Microsoft |
Microsoft SQL Server 2017 for x64-based Systems (CU31) |
14.0.3006.16
< 14.0.3560.2
|
|
CVE-2026-68883 |
high
|
8.5 |
0.0056
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2200.2
|
|
CVE-2026-68883 |
high
|
8.5 |
0.0056
|
Microsoft |
Microsoft SQL Server 2019 for x64-based Systems (CU32) |
15.0.4003.23
< 15.0.4500.2
|
|
CVE-2026-68883 |
high
|
8.5 |
0.0056
|
Microsoft |
Microsoft SQL Server 2022 (GDR) |
16.0.0
< 16.0.1210.3
|
|
CVE-2026-68883 |
high
|
8.5 |
0.0056
|
Microsoft |
Microsoft SQL Server 2022 for x64-based Systems (CU27) |
16.0.4003.1
< 16.0.4305.5
|
|
CVE-2026-68883 |
high
|
8.5 |
0.0056
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (CU9) |
17.0.4006.2
< 17.0.5015.4
|
|
CVE-2026-68883 |
high
|
8.5 |
0.0056
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1145.4
|
|
CVE-2026-85886 |
high
|
8.5 |
0.0040
|
Microsoft |
Microsoft SQL Server 2017 for x64-based Systems (CU31) |
14.0.3006.16
< 14.0.3560.2
|
|
CVE-2026-85886 |
high
|
8.5 |
0.0040
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2200.2
|
|
CVE-2026-85886 |
high
|
8.5 |
0.0040
|
Microsoft |
Microsoft SQL Server 2019 for x64-based Systems (CU32) |
15.0.4003.23
< 15.0.4500.2
|
|
CVE-2026-85886 |
high
|
8.5 |
0.0040
|
Microsoft |
Microsoft SQL Server 2022 (GDR) |
16.0.0
< 16.0.1210.3
|
|
CVE-2026-85886 |
high
|
8.5 |
0.0040
|
Microsoft |
Microsoft SQL Server 2022 for x64-based Systems (CU27) |
16.0.4003.1
< 16.0.4305.5
|
|
CVE-2026-85886 |
high
|
8.5 |
0.0040
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (CU9) |
17.0.4006.2
< 17.0.5015.4
|
|
CVE-2026-85886 |
high
|
8.5 |
0.0040
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1145.4
|
|
CVE-2026-32162 |
high
|
8.4 |
0.0192
|
microsoft |
windows_server_2019 |
< 10.0.17763.8644
|
|
CVE-2026-32162 |
high
|
8.4 |
0.0192
|
microsoft |
windows_server_2022 |
< 10.0.20348.5020
|
|
CVE-2026-32162 |
high
|
8.4 |
0.0192
|
microsoft |
windows_server_2022_23h2 |
< 10.0.25398.2274
|
|
CVE-2026-32162 |
high
|
8.4 |
0.0192
|
microsoft |
windows_server_2025 |
< 10.0.26100.32690
|
|
CVE-2026-40367 |
high
|
8.4 |
0.0045
|
microsoft |
sharepoint_server |
< 16.0.19725.20280
|
|
CVE-2026-40367 |
high
|
8.4 |
0.0045
|
microsoft |
sharepoint_server |
2016
|
|
CVE-2026-40367 |
high
|
8.4 |
0.0045
|
microsoft |
sharepoint_server |
2019
|
|
CVE-2026-46508 |
high
|
8.4 |
0.0016
|
vercel |
turborepo_language_server_protocol |
< 2.9.14000
|
|
CVE-2026-49184 |
high
|
8.4 |
0.0034
|
microsoft |
windows_server_2012 |
-
|
|
CVE-2026-49184 |
high
|
8.4 |
0.0034
|
microsoft |
windows_server_2012 |
r2
|
|
CVE-2026-49184 |
high
|
8.4 |
0.0034
|
microsoft |
windows_server_2016 |
< 10.0.14393.9339
|
|
CVE-2026-49184 |
high
|
8.4 |
0.0034
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|
CVE-2026-49184 |
high
|
8.4 |
0.0034
|
microsoft |
windows_server_2022 |
< 10.0.20348.5386
|
|
CVE-2026-49184 |
high
|
8.4 |
0.0034
|
microsoft |
windows_server_2025 |
< 10.0.26100.33158
|
|
CVE-2026-54122 |
high
|
8.4 |
0.0036
|
microsoft |
windows_server_2012 |
-
|
|
CVE-2026-54122 |
high
|
8.4 |
0.0036
|
microsoft |
windows_server_2012 |
r2
|
|
CVE-2026-54122 |
high
|
8.4 |
0.0036
|
microsoft |
windows_server_2016 |
< 10.0.14393.9339
|
|
CVE-2026-54122 |
high
|
8.4 |
0.0036
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|