Local code execution via NTFS heap overflow
Published Jan 13, 2026 · Updated Jan 13, 2026
Heap-based buffer overflow in Windows NTFS allows local users to execute code on affected systems through an undisclosed vector. Microsoft identifies NTFS as the affected component but has not disclosed the function, input path, or faulty bounds operation that corrupts heap memory. Low-privileged local access is required, and successful exploitation executes code in the vulnerable component's security context.
Summary
What happened
Heap-based buffer overflow in Windows NTFS allows local users to execute code on affected systems through an undisclosed vector. Microsoft identifies NTFS as the affected component but has not disclosed the function, input path, or faulty bounds operation that corrupts heap memory. Low-privileged local access is required, and successful exploitation executes code in the vulnerable component's security context.
The record
- CVE
- CVE-2026-20922
- Published
- Jan 13, 2026
- Updated
- Jan 13, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-122
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 13, 2026CVE publishedPublication date reported by the CVE source.
- Jan 13, 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=10.0.17763.0 <10.0.17763.8276
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