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
|
|
CVE-2026-67636 |
critical
|
9.0 |
0.0071
|
Microsoft |
Microsoft SQL Server 2025 (CU8) |
17.0.0.0
< 17.0.4085.5
|
|
CVE-2026-67636 |
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-47295 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2016 Service Pack 3 (GDR) |
13.0.0
< 13.0.6500.1
|
|
CVE-2026-55002 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2016 Service Pack 3 (GDR) |
13.0.0
< 13.0.6500.1
|
|
CVE-2026-94512 |
high
|
8.8 |
0.0065
|
Microsoft |
Microsoft SQL Server 2017 (GDR) |
14.0.0
< 14.0.2140.2
|
|
CVE-2026-65674 |
high
|
8.8 |
0.0162
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2200.2
|
|
CVE-2026-40370 |
high
|
8.8 |
0.0056
|
microsoft |
sql_server_2016 |
< 13.0.6490.1
|
|
CVE-2026-40370 |
high
|
8.8 |
0.0056
|
microsoft |
sql_server_2017 |
< 14.0.2110.2
|
|
CVE-2026-40370 |
high
|
8.8 |
0.0056
|
microsoft |
sql_server_2019 |
< 15.0.2170.1
|
|
CVE-2026-40370 |
high
|
8.8 |
0.0056
|
microsoft |
sql_server_2022 |
< 16.0.1180.1
|
|
CVE-2026-40370 |
high
|
8.8 |
0.0056
|
microsoft |
sql_server_2025 |
< 17.0.1115.1
|
|
CVE-2026-8659 |
high
|
8.8 |
0.0129
|
rapid7 |
insightconnect_sqlmap |
< 2.0.1
|
|
CVE-2026-55002 |
high
|
8.8 |
0.0091
|
microsoft |
sql_server_2016 |
< 13.0.6500.1
|
|
CVE-2026-55002 |
high
|
8.8 |
0.0091
|
microsoft |
sql_server_2017 |
< 14.0.2120.1
|
|
CVE-2026-55002 |
high
|
8.8 |
0.0091
|
microsoft |
sql_server_2019 |
< 15.0.2180.2
|
|
CVE-2026-55002 |
high
|
8.8 |
0.0091
|
microsoft |
sql_server_2022 |
< 16.0.1190.2
|
|
CVE-2026-55002 |
high
|
8.8 |
0.0091
|
microsoft |
sql_server_2025 |
< 17.0.1125.2
|
|
CVE-2026-47295 |
high
|
8.8 |
0.0099
|
microsoft |
sql_server_2016 |
< 13.0.6500.1
|
|
CVE-2026-47295 |
high
|
8.8 |
0.0099
|
microsoft |
sql_server_2017 |
< 14.0.2120.1
|
|
CVE-2026-47295 |
high
|
8.8 |
0.0099
|
microsoft |
sql_server_2019 |
< 15.0.2180.2
|
|
CVE-2026-47295 |
high
|
8.8 |
0.0099
|
microsoft |
sql_server_2022 |
< 16.0.1190.2
|
|
CVE-2026-47295 |
high
|
8.8 |
0.0099
|
microsoft |
sql_server_2025 |
< 17.0.1125.2
|
|
CVE-2026-62895 |
high
|
8.8 |
0.0080
|
microsoft |
azure_arc__sql_server_extension |
< 1.1.3518.465
|
|
CVE-2026-67368 |
high
|
8.8 |
0.0102
|
microsoft |
sql_server_2017 |
< 14.0.2130.4
|
|
CVE-2026-67368 |
high
|
8.8 |
0.0102
|
microsoft |
sql_server_2019 |
< 15.0.2190.7
|
|
CVE-2026-67368 |
high
|
8.8 |
0.0102
|
microsoft |
sql_server_2022 |
< 16.0.1200.5
|
|
CVE-2026-67368 |
high
|
8.8 |
0.0102
|
microsoft |
sql_server_2025 |
< 17.0.1135.8
|
|
CVE-2026-67370 |
high
|
8.8 |
0.0099
|
microsoft |
sql_server_2017 |
< 14.0.2130.4
|
|
CVE-2026-67370 |
high
|
8.8 |
0.0099
|
microsoft |
sql_server_2019 |
< 15.0.2190.7
|
|
CVE-2026-67370 |
high
|
8.8 |
0.0099
|
microsoft |
sql_server_2022 |
< 16.0.1200.5
|
|
CVE-2026-67370 |
high
|
8.8 |
0.0099
|
microsoft |
sql_server_2025 |
< 17.0.1135.8
|
|
CVE-2026-67373 |
high
|
8.8 |
0.0091
|
microsoft |
sql_server_2025 |
< 17.0.1135.8
|
|
CVE-2026-77482 |
high
|
8.8 |
0.0082
|
microsoft |
sql_server_2017 |
< 14.0.2130.4
|
|
CVE-2026-77482 |
high
|
8.8 |
0.0082
|
microsoft |
sql_server_2019 |
< 15.0.2190.7
|
|
CVE-2026-101781 |
high
|
8.8 |
0.0039
|
oracle |
mysql_cluster |
< 8.0.49
|
|
CVE-2026-101781 |
high
|
8.8 |
0.0039
|
oracle |
mysql_server |
< 8.4.12
|
|
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 (GDR) |
15.0.0
< 15.0.2200.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 (GDR) |
16.0.0
< 16.0.1210.3
|
|
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
|
|