Authenticated local code execution via heap-based buffer overflow
Published Sep 8, 2026 · Updated Sep 10, 2026
Heap-based buffer overflow in Microsoft SQL Server 2017, 2019, 2022, and 2025 allows local users to execute arbitrary code. Microsoft identifies the defect as a heap overrun but has not disclosed the affected function, input field, or operation that mishandles attacker-controlled data. Successful exploitation requires local access and low privileges; resulting code can affect data confidentiality, integrity, and service availability.
Summary
What happened
Heap-based buffer overflow in Microsoft SQL Server 2017, 2019, 2022, and 2025 allows local users to execute arbitrary code. Microsoft identifies the defect as a heap overrun but has not disclosed the affected function, input field, or operation that mishandles attacker-controlled data. Successful exploitation requires local access and low privileges; resulting code can affect data confidentiality, integrity, and service availability.
The record
- CVE
- CVE-2026-68787
- Published
- Sep 8, 2026
- Updated
- Sep 10, 2026
- Vendor
- Microsoft
- Product
- Microsoft SQL Server 2022
- Classifications
- CWE-122
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=16.0.0.0 <16.0.4275.2
- Affected versionversion=16.0.0 <16.0.1200.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo