Security-feature bypass via insufficient audit logging
Published Sep 8, 2026 · Updated Sep 10, 2026
Insufficient logging in Microsoft SQL Server 2022 and 2025 allows remote authenticated users to bypass a security feature. Microsoft identifies the flaw only as insufficient logging and has not disclosed the affected logging path, omitted event, or bypassed control. A low-privilege network session and no user interaction are required, and successful exploitation exposes confidential data without reported integrity or availability impact.
Summary
What happened
Insufficient logging in Microsoft SQL Server 2022 and 2025 allows remote authenticated users to bypass a security feature. Microsoft identifies the flaw only as insufficient logging and has not disclosed the affected logging path, omitted event, or bypassed control. A low-privilege network session and no user interaction are required, and successful exploitation exposes confidential data without reported integrity or availability impact.
The record
- CVE
- CVE-2026-66816
- Published
- Sep 8, 2026
- Updated
- Sep 10, 2026
- Vendor
- Microsoft
- Product
- Microsoft SQL Server 2022
- Classifications
- CWE-778
- Attack vector
- network
- 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?
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