Local code execution via NTFS heap overflow
Published Jul 14, 2026 · Updated Jul 14, 2026
Heap-based buffer overflow in Windows NTFS across affected Windows releases allows local users to execute code through local access. Microsoft identifies NTFS as the locus but has not disclosed the malformed input, affected routine, or incorrect bounds operation that overwrites heap memory. Exploitation requires low-privileged local access, needs no user interaction, and can compromise confidentiality, integrity, and availability within the affected security authority.
Summary
What happened
Heap-based buffer overflow in Windows NTFS across affected Windows releases allows local users to execute code through local access. Microsoft identifies NTFS as the locus but has not disclosed the malformed input, affected routine, or incorrect bounds operation that overwrites heap memory. Exploitation requires low-privileged local access, needs no user interaction, and can compromise confidentiality, integrity, and availability within the affected security authority.
The record
- CVE
- CVE-2026-50494
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-122
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 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.9020
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