CVE-2026-68781 json
Microsoft SQL Server Information Disclosure Vulnerability
published 2026-09-08 2 mo ago modified 2026-10-31 8 d ago also EUVD-2026-73187
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 0
- none known
Summary
Out-of-bounds read in SQL Server allows an authorized attacker to disclose information over a network.
Patch / fix
- Microsoft Microsoft SQL Server 2017 (CU 31) 14.0.3550.4
- Microsoft Microsoft SQL Server 2017 (GDR) 14.0.2130.4
- Microsoft Microsoft SQL Server 2019 (CU 32) 15.0.4490.9
- Microsoft Microsoft SQL Server 2019 (GDR) 15.0.2190.7
- Microsoft Microsoft SQL Server 2022 (CU 26) 16.0.4275.2
- Microsoft Microsoft SQL Server 2022 (GDR) 16.0.1200.5
- Microsoft Microsoft SQL Server 2025 (CU8) 17.0.4085.5
- Microsoft Microsoft SQL Server 2025 for x64-based Systems (GDR) 17.0.1135.8
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
1.00% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- Microsoft Microsoft SQL Server 2017 (CU 31)
- Microsoft Microsoft SQL Server 2017 (GDR)
- Microsoft Microsoft SQL Server 2019 (CU 32)
- Microsoft Microsoft SQL Server 2019 (GDR)
- Microsoft Microsoft SQL Server 2022 (CU 26)
- Microsoft Microsoft SQL Server 2022 (GDR)
- Microsoft Microsoft SQL Server 2025 (CU8)
- Microsoft Microsoft SQL Server 2025 for x64-based Systems (GDR)
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
- Technology feeds
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2026-68781
vendor-advisory, patch
Sources
- CVE List CVE-2026-68781
- NVD CVE-2026-68781
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.