CVE-2026-66818 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft SQL Server 2019 (CU 32) |
15.0.0.0
< 15.0.4490.9
|
|
CVE-2026-66818 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2190.7
|
|
CVE-2026-66818 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft SQL Server 2022 (CU 26) |
16.0.0.0
< 16.0.4275.2
|
|
CVE-2026-66818 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft SQL Server 2022 (GDR) |
16.0.0
< 16.0.1200.5
|
|
CVE-2026-66818 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft SQL Server 2025 (CU8) |
17.0.0.0
< 17.0.4085.5
|
|
CVE-2026-66818 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1135.8
|
|
CVE-2026-66820 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2017 (CU 31) |
14.0.0
< 14.0.3550.4
|
|
CVE-2026-66820 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2017 (GDR) |
14.0.0
< 14.0.2130.4
|
|
CVE-2026-66820 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2019 (CU 32) |
15.0.0.0
< 15.0.4490.9
|
|
CVE-2026-66820 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2190.7
|
|
CVE-2026-66820 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2022 (CU 26) |
16.0.0.0
< 16.0.4275.2
|
|
CVE-2026-66820 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2022 (GDR) |
16.0.0
< 16.0.1200.5
|
|
CVE-2026-66820 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2025 (CU8) |
17.0.0.0
< 17.0.4085.5
|
|
CVE-2026-66820 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1135.8
|
|
CVE-2026-67368 |
high
|
8.8 |
0.0102
|
Microsoft |
Microsoft SQL Server 2017 (CU 31) |
14.0.0
< 14.0.3550.4
|
|
CVE-2026-67368 |
high
|
8.8 |
0.0102
|
Microsoft |
Microsoft SQL Server 2017 (GDR) |
14.0.0
< 14.0.2130.4
|
|
CVE-2026-67368 |
high
|
8.8 |
0.0102
|
Microsoft |
Microsoft SQL Server 2019 (CU 32) |
15.0.0.0
< 15.0.4490.9
|
|
CVE-2026-67368 |
high
|
8.8 |
0.0102
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2190.7
|
|
CVE-2026-67368 |
high
|
8.8 |
0.0102
|
Microsoft |
Microsoft SQL Server 2022 (CU 26) |
16.0.0.0
< 16.0.4275.2
|
|
CVE-2026-67368 |
high
|
8.8 |
0.0102
|
Microsoft |
Microsoft SQL Server 2022 (GDR) |
16.0.0
< 16.0.1200.5
|
|
CVE-2026-67368 |
high
|
8.8 |
0.0102
|
Microsoft |
Microsoft SQL Server 2025 (CU8) |
17.0.0.0
< 17.0.4085.5
|
|
CVE-2026-67368 |
high
|
8.8 |
0.0102
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1135.8
|
|
CVE-2026-67370 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2017 (CU 31) |
14.0.0
< 14.0.3550.4
|
|
CVE-2026-67370 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2017 (GDR) |
14.0.0
< 14.0.2130.4
|
|
CVE-2026-67370 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2019 (CU 32) |
15.0.0.0
< 15.0.4490.9
|
|
CVE-2026-67370 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2190.7
|
|
CVE-2026-67370 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2022 (CU 26) |
16.0.0.0
< 16.0.4275.2
|
|
CVE-2026-67370 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2022 (GDR) |
16.0.0
< 16.0.1200.5
|
|
CVE-2026-67370 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2025 (CU8) |
17.0.0.0
< 17.0.4085.5
|
|
CVE-2026-67370 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1135.8
|
|
CVE-2026-67373 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2025 (CU8) |
17.0.0.0
< 17.0.4085.5
|
|
CVE-2026-67373 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1135.8
|
|
CVE-2026-67380 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2017 (CU 31) |
14.0.0
< 14.0.3550.4
|
|
CVE-2026-67380 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2017 (GDR) |
14.0.0
< 14.0.2130.4
|
|
CVE-2026-67380 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2019 (CU 32) |
15.0.0.0
< 15.0.4490.9
|
|
CVE-2026-67380 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2190.7
|
|
CVE-2026-67380 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2022 (CU 26) |
16.0.0.0
< 16.0.4275.2
|
|
CVE-2026-67380 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2022 (GDR) |
16.0.0
< 16.0.1200.5
|
|
CVE-2026-67380 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2025 (CU8) |
17.0.0.0
< 17.0.4085.5
|
|
CVE-2026-67380 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1135.8
|
|
CVE-2026-67381 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2017 (CU 31) |
14.0.0
< 14.0.3550.4
|
|
CVE-2026-67381 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2017 (GDR) |
14.0.0
< 14.0.2130.4
|
|
CVE-2026-67381 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2019 (CU 32) |
15.0.0.0
< 15.0.4490.9
|
|
CVE-2026-67381 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2190.7
|
|
CVE-2026-67381 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2022 (CU 26) |
16.0.0.0
< 16.0.4275.2
|
|
CVE-2026-67381 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2022 (GDR) |
16.0.0
< 16.0.1200.5
|
|
CVE-2026-67381 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2025 (CU8) |
17.0.0.0
< 17.0.4085.5
|
|
CVE-2026-67381 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1135.8
|
|
CVE-2026-67384 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2017 (CU 31) |
14.0.0
< 14.0.3550.4
|
|
CVE-2026-67384 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft SQL Server 2017 (GDR) |
14.0.0
< 14.0.2130.4
|
|