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-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 2016 Service Pack 3 (GDR) |
13.0.0
< 13.0.6500.1
|
|
CVE-2026-54118 |
critical
|
9.8 |
0.0153
|
Microsoft |
Microsoft SQL Server 2016 Service Pack 3 Azure Connect Feature Pack |
13.0.0
< 13.0.7095.1
|
|
CVE-2026-54118 |
critical
|
9.8 |
0.0153
|
Microsoft |
Microsoft SQL Server 2017 (CU 31) |
14.0.0
< 14.0.3540.1
|
|
CVE-2026-54118 |
critical
|
9.8 |
0.0153
|
Microsoft |
Microsoft SQL Server 2017 (GDR) |
14.0.0
< 14.0.2120.1
|
|
CVE-2026-54118 |
critical
|
9.8 |
0.0153
|
Microsoft |
Microsoft SQL Server 2019 (CU 32) |
15.0.0.0
< 15.0.4480.2
|
|
CVE-2026-54118 |
critical
|
9.8 |
0.0153
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2180.2
|
|
CVE-2026-54118 |
critical
|
9.8 |
0.0153
|
Microsoft |
Microsoft SQL Server 2022 (GDR) |
16.0.0
< 16.0.1190.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 (CU 6) |
17.0.4060.2
< 17.0.4060.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-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_2016 |
< 13.0.7095.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_2017 |
< 14.0.3540.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_2019 |
< 15.0.4480.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_2022 |
< 16.0.4262.2
|
|
CVE-2026-54117 |
critical
|
9.8 |
0.0153
|
microsoft |
sql_server_2025 |
< 17.0.1125.2
|
|
CVE-2026-54117 |
critical
|
9.8 |
0.0153
|
microsoft |
sql_server_2025 |
< 17.0.4060.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_2016 |
< 13.0.7095.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_2017 |
< 14.0.3540.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_2019 |
< 15.0.4480.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_2022 |
< 16.0.4262.2
|
|
CVE-2026-54118 |
critical
|
9.8 |
0.0153
|
microsoft |
sql_server_2025 |
< 17.0.1125.2
|
|
CVE-2026-54118 |
critical
|
9.8 |
0.0153
|
microsoft |
sql_server_2025 |
< 17.0.4060.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_2017 |
< 14.0.3550.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_2019 |
< 15.0.4490.9
|
|
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_2022 |
< 16.0.4275.2
|
|
CVE-2026-67631 |
critical
|
9.8 |
0.0097
|
microsoft |
sql_server_2025 |
< 17.0.1135.8
|
|
CVE-2026-67631 |
critical
|
9.8 |
0.0097
|
microsoft |
sql_server_2025 |
< 17.0.4085.5
|
|
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-47295 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2016 Service Pack 3 Azure Connect Feature Pack |
13.0.0
< 13.0.7095.1
|
|
CVE-2026-47295 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2017 (CU 31) |
14.0.0
< 14.0.3540.1
|
|
CVE-2026-47295 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2017 (GDR) |
14.0.0
< 14.0.2120.1
|
|
CVE-2026-47295 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2019 (CU 32) |
15.0.0.0
< 15.0.4480.2
|
|
CVE-2026-47295 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2180.2
|
|
CVE-2026-47295 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2022 (GDR) |
16.0.0
< 16.0.1190.2
|
|
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 (CU 6) |
17.0.4060.2
< 17.0.4060.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
|
|