CVE-2026-56162 |
critical
|
10.0 |
0.0090
|
Microsoft |
Azure SQL Database |
-
|
|
CVE-2026-69502 |
critical
|
10.0 |
0.0080
|
Microsoft |
Azure SQL Database |
-
|
|
CVE-2026-48772 |
critical
|
10.0 |
0.0023
|
proxysql |
proxysql |
< 3.0.9
|
|
CVE-2026-56162 |
critical
|
10.0 |
0.0090
|
microsoft |
azure_sql_database |
-
|
|
CVE-2026-69502 |
critical
|
10.0 |
0.0080
|
microsoft |
azure_sql_database |
-
|
|
CVE-2026-68782 |
critical
|
9.9 |
0.0099
|
Microsoft |
Azure SQL Database |
-
|
|
CVE-2026-68789 |
critical
|
9.9 |
0.0099
|
Microsoft |
Azure SQL Database |
-
|
|
CVE-2026-40342 |
critical
|
9.9 |
0.0069
|
firebirdsql |
firebird |
< 3.0.14
|
|
CVE-2026-46850 |
critical
|
9.9 |
0.0052
|
oracle |
mysql_shell |
2026.2.0
|
|
CVE-2026-68782 |
critical
|
9.9 |
0.0099
|
microsoft |
azure_sql_database |
-
|
|
CVE-2026-68789 |
critical
|
9.9 |
0.0099
|
microsoft |
azure_sql_database |
-
|
|
CVE-2026-54117 |
critical
|
9.8 |
0.0153
|
Microsoft |
Microsoft SQL Server 2025 (CU 6) |
17.0.4060.2
< 17.0.4060.2
|
|
CVE-2026-54118 |
critical
|
9.8 |
0.0153
|
Microsoft |
Microsoft SQL Server 2016 Service Pack 3 (GDR) |
13.0.0
< 13.0.6500.1
|
|
CVE-2026-46860 |
critical
|
9.8 |
0.0047
|
oracle |
mysql_router |
< 9.7.0
|
|
CVE-2026-48773 |
critical
|
9.8 |
0.0069
|
proxysql |
proxysql |
< 3.0.9
|
|
CVE-2026-54117 |
critical
|
9.8 |
0.0153
|
microsoft |
sql_server_2016 |
< 13.0.6500.1
|
|
CVE-2026-54117 |
critical
|
9.8 |
0.0153
|
microsoft |
sql_server_2017 |
< 14.0.2120.1
|
|
CVE-2026-54117 |
critical
|
9.8 |
0.0153
|
microsoft |
sql_server_2019 |
< 15.0.2180.2
|
|
CVE-2026-54117 |
critical
|
9.8 |
0.0153
|
microsoft |
sql_server_2022 |
< 16.0.1190.2
|
|
CVE-2026-54117 |
critical
|
9.8 |
0.0153
|
microsoft |
sql_server_2025 |
< 17.0.1125.2
|
|
CVE-2026-54118 |
critical
|
9.8 |
0.0153
|
microsoft |
sql_server_2016 |
< 13.0.6500.1
|
|
CVE-2026-54118 |
critical
|
9.8 |
0.0153
|
microsoft |
sql_server_2017 |
< 14.0.2120.1
|
|
CVE-2026-54118 |
critical
|
9.8 |
0.0153
|
microsoft |
sql_server_2019 |
< 15.0.2180.2
|
|
CVE-2026-54118 |
critical
|
9.8 |
0.0153
|
microsoft |
sql_server_2022 |
< 16.0.1190.2
|
|
CVE-2026-54118 |
critical
|
9.8 |
0.0153
|
microsoft |
sql_server_2025 |
< 17.0.1125.2
|
|
CVE-2026-67631 |
critical
|
9.8 |
0.0097
|
microsoft |
sql_server_2017 |
< 14.0.2130.4
|
|
CVE-2026-67631 |
critical
|
9.8 |
0.0097
|
microsoft |
sql_server_2019 |
< 15.0.2190.7
|
|
CVE-2026-67631 |
critical
|
9.8 |
0.0097
|
microsoft |
sql_server_2022 |
< 16.0.1200.5
|
|
CVE-2026-67631 |
critical
|
9.8 |
0.0097
|
microsoft |
sql_server_2025 |
< 17.0.1135.8
|
|
CVE-2026-61620 |
critical
|
9.8 |
0.0039
|
seancorfield |
honeysql |
>= 2.0.0, < 2.7.1392
|
|
CVE-2026-67631 |
critical
|
9.8 |
0.0097
|
Microsoft |
Microsoft SQL Server 2017 (CU 31) |
14.0.0
< 14.0.3550.4
|
|
CVE-2026-67631 |
critical
|
9.8 |
0.0097
|
Microsoft |
Microsoft SQL Server 2017 (GDR) |
14.0.0
< 14.0.2130.4
|
|
CVE-2026-67631 |
critical
|
9.8 |
0.0097
|
Microsoft |
Microsoft SQL Server 2019 (CU 32) |
15.0.0.0
< 15.0.4490.9
|
|
CVE-2026-67631 |
critical
|
9.8 |
0.0097
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2190.7
|
|
CVE-2026-67631 |
critical
|
9.8 |
0.0097
|
Microsoft |
Microsoft SQL Server 2022 (CU 26) |
16.0.0.0
< 16.0.4275.2
|
|
CVE-2026-67631 |
critical
|
9.8 |
0.0097
|
Microsoft |
Microsoft SQL Server 2022 (GDR) |
16.0.0
< 16.0.1200.5
|
|
CVE-2026-67631 |
critical
|
9.8 |
0.0097
|
Microsoft |
Microsoft SQL Server 2025 (CU8) |
17.0.0.0
< 17.0.4085.5
|
|
CVE-2026-67631 |
critical
|
9.8 |
0.0097
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1135.8
|
|
CVE-2026-67643 |
critical
|
9.8 |
0.0097
|
Microsoft |
Microsoft SQL Server 2022 (CU 26) |
16.0.0.0
< 16.0.4275.2
|
|
CVE-2026-67643 |
critical
|
9.8 |
0.0097
|
Microsoft |
Microsoft SQL Server 2022 (GDR) |
16.0.0
< 16.0.1200.5
|
|
CVE-2026-67643 |
critical
|
9.8 |
0.0097
|
Microsoft |
Microsoft SQL Server 2025 (CU8) |
17.0.0.0
< 17.0.4085.5
|
|
CVE-2026-67643 |
critical
|
9.8 |
0.0097
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1135.8
|
|
CVE-2026-45321 |
critical
|
9.6 |
0.0328
|
kilbot |
tallyui\/storage-sqlite |
0.2.1
|
KEV
|
CVE-2026-45321 |
critical
|
9.6 |
0.0328
|
kilbot |
tallyui\/storage-sqlite |
0.2.2
|
KEV
|
CVE-2026-45321 |
critical
|
9.6 |
0.0328
|
kilbot |
tallyui\/storage-sqlite |
0.2.3
|
KEV
|
CVE-2026-46861 |
critical
|
9.6 |
0.0036
|
oracle |
mysql_ndb_cluster |
< 8.0.46
|
|
CVE-2026-65669 |
critical
|
9.6 |
0.0086
|
Microsoft |
SQL Server Management Studio 22 |
22.0
< 22.8.2
|
|
CVE-2026-66309 |
critical
|
9.1 |
0.0086
|
Microsoft |
Azure SQL Database |
-
|
|
CVE-2026-66309 |
critical
|
9.1 |
0.0086
|
microsoft |
azure_sql_database |
-
|
|
CVE-2026-67378 |
critical
|
9.0 |
0.0071
|
Microsoft |
Microsoft SQL Server 2019 (CU 32) |
15.0.0.0
< 15.0.4490.9
|
|