CVE-2026-54117 |
critical
|
9.8 |
0.0153
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1125.2
|
|
CVE-2026-54118 |
critical
|
9.8 |
0.0153
|
Microsoft |
Microsoft SQL Server 2022 for x64-based Systems (CU 25) |
16.0.4260.1
< 16.0.4262.2
|
|
CVE-2026-54118 |
critical
|
9.8 |
0.0153
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1125.2
|
|
CVE-2026-58289 |
critical
|
9.0 |
0.0199
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-50736 |
critical
|
9.0 |
0.0041
|
enterprisedb |
pglogical |
< 2.4.8
|
|
CVE-2026-50737 |
critical
|
9.0 |
0.0040
|
enterprisedb |
pglogical |
< 2.4.8
|
|
CVE-2026-83831 |
high
|
8.8 |
0.0077
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 154.0.4258.48
|
|
CVE-2026-85898 |
high
|
8.8 |
0.0077
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 154.0.4258.48
|
|
CVE-2026-72984 |
high
|
8.8 |
0.0082
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 152.0.4191.53
|
|
CVE-2026-47295 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2022 for x64-based Systems (CU 25) |
16.0.4260.1
< 16.0.4262.2
|
|
CVE-2026-47295 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1125.2
|
|
CVE-2026-55002 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2022 for x64-based Systems (CU 25) |
16.0.4260.1
< 16.0.4262.2
|
|
CVE-2026-55002 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1125.2
|
|
CVE-2026-56645 |
high
|
8.8 |
0.0082
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-57974 |
high
|
8.8 |
0.0082
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-57981 |
high
|
8.8 |
0.0082
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-94512 |
high
|
8.8 |
0.0065
|
Microsoft |
Microsoft SQL Server 2017 for x64-based Systems (CU31) |
14.0.3006.16
< 14.0.3560.2
|
|
CVE-2026-94512 |
high
|
8.8 |
0.0065
|
Microsoft |
Microsoft SQL Server 2019 for x64-based Systems (CU32) |
15.0.4003.23
< 15.0.4500.2
|
|
CVE-2026-94512 |
high
|
8.8 |
0.0065
|
Microsoft |
Microsoft SQL Server 2022 for x64-based Systems (CU27) |
16.0.4003.1
< 16.0.4305.5
|
|
CVE-2026-94512 |
high
|
8.8 |
0.0065
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (CU9) |
17.0.4006.2
< 17.0.5015.4
|
|
CVE-2026-94512 |
high
|
8.8 |
0.0065
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1145.4
|
|
CVE-2026-108400 |
high
|
8.8 |
0.0091
|
Microsoft |
HEVC Video Extensions for Licensed Applications |
2.0.0.0
< 2.4.85.0
|
|
CVE-2026-65674 |
high
|
8.8 |
0.0162
|
Microsoft |
Microsoft SQL Server 2019 for x64-based Systems (CU32) |
15.0.4003.23
< 15.0.4500.2
|
|
CVE-2026-65674 |
high
|
8.8 |
0.0162
|
Microsoft |
Microsoft SQL Server 2022 for x64-based Systems (CU27) |
16.0.4003.1
< 16.0.4305.5
|
|
CVE-2026-65674 |
high
|
8.8 |
0.0162
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (CU9) |
17.0.4006.2
< 17.0.5015.4
|
|
CVE-2026-65674 |
high
|
8.8 |
0.0162
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1145.4
|
|
CVE-2026-9155 |
high
|
8.8 |
0.0160
|
gnu |
sed |
4.2.2
|
|
CVE-2026-88077 |
high
|
8.8 |
—
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 154.0.4258.62
|
|
CVE-2026-96192 |
high
|
8.8 |
—
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 155.0.4283.45
|
|
CVE-2026-96196 |
high
|
8.8 |
—
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 156.0.4314.50
|
|
CVE-2026-96203 |
high
|
8.8 |
—
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 155.0.4283.45
|
|
CVE-2026-96202 |
high
|
8.8 |
0.0093
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 154.0.4258.37
|
|
CVE-2026-96951 |
high
|
8.8 |
0.0981
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 154.0.4258.62
|
KEV
|
CVE-2026-85890 |
high
|
8.8 |
—
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 154.0.4258.37
|
|
CVE-2026-85897 |
high
|
8.8 |
—
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 154.0.4258.37
|
|
CVE-2026-96198 |
high
|
8.8 |
—
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 154.0.4258.37
|
|
CVE-2026-96199 |
high
|
8.8 |
—
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 154.0.4258.37
|
|
CVE-2026-83831 |
high
|
8.8 |
0.0077
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 154.0.4258.37
|
|
CVE-2026-57983 |
high
|
8.7 |
0.0065
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-70341 |
high
|
8.5 |
0.0064
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 152.0.4191.52
|
|
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 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 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 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 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
|
|