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-55002 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2016 Service Pack 3 Azure Connect Feature Pack |
13.0.0
< 13.0.7095.1
|
|
CVE-2026-55002 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2017 (CU 31) |
14.0.0
< 14.0.3540.1
|
|
CVE-2026-55002 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2017 (GDR) |
14.0.0
< 14.0.2120.1
|
|
CVE-2026-55002 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2019 (CU 32) |
15.0.0.0
< 15.0.4480.2
|
|
CVE-2026-55002 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2180.2
|
|
CVE-2026-55002 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2022 (GDR) |
16.0.0
< 16.0.1190.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 (CU 6) |
17.0.4060.2
< 17.0.4060.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-94512 |
high
|
8.8 |
0.0065
|
Microsoft |
Microsoft SQL Server 2017 (GDR) |
14.0.0
< 14.0.2140.2
|
|
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
|
|
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-65674 |
high
|
8.8 |
0.0162
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2200.2
|
|
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 (GDR) |
16.0.0
< 16.0.1210.3
|
|
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-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_2016 |
< 13.0.7085.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_2017 |
< 14.0.3530.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_2019 |
< 15.0.4470.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_2022 |
< 16.0.4252.3
|
|
CVE-2026-40370 |
high
|
8.8 |
0.0056
|
microsoft |
sql_server_2025 |
< 17.0.1115.1
|
|
CVE-2026-40370 |
high
|
8.8 |
0.0056
|
microsoft |
sql_server_2025 |
< 17.0.4040.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_2016 |
< 13.0.7095.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_2017 |
< 14.0.3540.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_2019 |
< 15.0.4480.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_2022 |
< 16.0.4262.2
|
|
CVE-2026-55002 |
high
|
8.8 |
0.0091
|
microsoft |
sql_server_2025 |
< 17.0.1125.2
|
|
CVE-2026-55002 |
high
|
8.8 |
0.0091
|
microsoft |
sql_server_2025 |
< 17.0.4060.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_2016 |
< 13.0.7095.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_2017 |
< 14.0.3540.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_2019 |
< 15.0.4480.2
|
|