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-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-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-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-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-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-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-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-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-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-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
|
|
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_2019 |
< 15.0.4490.9
|
|
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_2019 |
< 15.0.4490.9
|
|
CVE-2026-77482 |
high
|
8.8 |
0.0082
|
microsoft |
sql_server_2019 |
< 15.0.2190.7
|
|
CVE-2026-77482 |
high
|
8.8 |
0.0082
|
microsoft |
sql_server_2019 |
< 15.0.4490.9
|
|
CVE-2026-67625 |
high
|
8.5 |
0.0056
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2200.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-68883 |
high
|
8.5 |
0.0056
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2200.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-85886 |
high
|
8.5 |
0.0040
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2200.2
|
|
CVE-2026-85886 |
high
|
8.5 |
0.0040
|
Microsoft |
Microsoft SQL Server 2019 for x64-based Systems (CU32) |
15.0.4003.23
< 15.0.4500.2
|
|
CVE-2026-96956 |
high
|
8.0 |
0.0060
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2200.2
|
|
CVE-2026-96956 |
high
|
8.0 |
0.0060
|
Microsoft |
Microsoft SQL Server 2019 for x64-based Systems (CU32) |
15.0.4003.23
< 15.0.4500.2
|
|
CVE-2026-32167 |
high
|
7.8 |
0.0030
|
microsoft |
sql_server_2019 |
< 15.0.2165.1
|
|
CVE-2026-32167 |
high
|
7.8 |
0.0030
|
microsoft |
sql_server_2019 |
< 15.0.4465.1
|
|
CVE-2026-32176 |
high
|
7.8 |
0.0025
|
microsoft |
sql_server_2019 |
< 15.0.2165.1
|
|
CVE-2026-32176 |
high
|
7.8 |
0.0025
|
microsoft |
sql_server_2019 |
< 15.0.4465.1
|
|
CVE-2026-85888 |
high
|
7.7 |
0.0080
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2200.2
|
|
CVE-2026-85888 |
high
|
7.7 |
0.0080
|
Microsoft |
Microsoft SQL Server 2019 for x64-based Systems (CU32) |
15.0.4003.23
< 15.0.4500.2
|
|
CVE-2026-88081 |
high
|
7.7 |
0.0080
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2200.2
|
|
CVE-2026-88081 |
high
|
7.7 |
0.0080
|
Microsoft |
Microsoft SQL Server 2019 for x64-based Systems (CU32) |
15.0.4003.23
< 15.0.4500.2
|
|
CVE-2026-47296 |
high
|
7.5 |
0.0069
|
Microsoft |
Microsoft SQL Server 2019 (CU 32) |
15.0.0.0
< 15.0.4480.2
|
|
CVE-2026-47296 |
high
|
7.5 |
0.0069
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2180.2
|
|
CVE-2026-47296 |
high
|
7.5 |
0.0069
|
microsoft |
sql_server_2019 |
< 15.0.2180.2
|
|
CVE-2026-47296 |
high
|
7.5 |
0.0069
|
microsoft |
sql_server_2019 |
< 15.0.4480.2
|
|
CVE-2026-85919 |
high
|
7.0 |
0.0024
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2200.2
|
|
CVE-2026-85919 |
high
|
7.0 |
0.0024
|
Microsoft |
Microsoft SQL Server 2019 for x64-based Systems (CU32) |
15.0.4003.23
< 15.0.4500.2
|
|