CVE-2026-68779: Microsoft SQL Server Information Disclosure Vulnerability
Published Sep 8, 2026
·Updated
Microsoft SQL Server Information Disclosure Vulnerability
Other sources
Out-of-bounds read in SQL Server allows an authorized attacker to disclose information over a network.
— Microsoft
Affected Software
16 affected componentsFixes available
Microsoft SQL Server 2022 (CU 26)<16.0.4275.2
16.0.4275.2
Microsoft SQL Server 2025 (CU8)<17.0.4085.5
17.0.4085.5
Microsoft SQL Server 2025<17.0.1135.8
17.0.1135.8
Microsoft SQL Server 2017<14.0.2130.4
14.0.2130.4
Microsoft SQL Server 2019 (CU 32)<15.0.4490.9
15.0.4490.9
Microsoft SQL Server 2022<16.0.1200.5
16.0.1200.5
Microsoft SQL Server 2019<15.0.2190.7
15.0.2190.7
Microsoft SQL Server 2017 (CU 31)<14.0.3550.4
14.0.3550.4
Microsoft SQL Server 2017<14.0.2130.4
Microsoft SQL Server 2017>=14.0.3006.16<14.0.3550.4
Microsoft SQL Server 2019<15.0.2190.7
Microsoft SQL Server 2019>=15.0.4003.23<15.0.4490.9
Microsoft SQL Server 2022<16.0.1200.5
Microsoft SQL Server 2022>=16.0.4003.1<16.0.4275.2
Microsoft SQL Server 2025<17.0.1135.8
Microsoft SQL Server 2025>=17.0.4006.2<17.0.4085.5
Remediation
Event History
Sep 8, 2026
CVE Published
via Microsoft·02:00 PM
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·05:14 PM
Data Sourced
via MITRE·05:14 PM
DescriptionSeverity
Data Sourced
via NVD·06:18 PM
RemedyDescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What level of access does an attacker need?
The attacker must be authorized and able to reach the SQL Server instance over the network. No user interaction is required.
2
Which SQL Server deployments are listed as affected?
The affected software list includes Microsoft SQL Server 2017, 2019, 2022, and 2025, including SQL Server 2017 CU 31, SQL Server 2019 CU 32, SQL Server 2022 CU 26, and SQL Server 2025 CU8.
3
How can I determine whether an instance is in scope?
Identify the SQL Server product version and cumulative update level installed on each instance, then compare it with the affected software list. Instances running one of the listed versions or cumulative updates should be treated as in scope.