Physical code execution via ReFS heap overflow
Published Jul 14, 2026 · Updated Jul 14, 2026
Heap-based buffer overflow in Microsoft Windows ReFS allows physically proximate attackers to execute code through physical access. Microsoft has not disclosed the specific ReFS parser locus or the unchecked size operation that overwrites heap memory. A physically present attacker needs no authentication or user interaction; successful exploitation grants code execution with full data and service impact.
Summary
What happened
Heap-based buffer overflow in Microsoft Windows ReFS allows physically proximate attackers to execute code through physical access. Microsoft has not disclosed the specific ReFS parser locus or the unchecked size operation that overwrites heap memory. A physically present attacker needs no authentication or user interaction; successful exploitation grants code execution with full data and service impact.
The record
- CVE
- CVE-2026-50492
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-122
- Attack vector
- physical
- Privileges
- unauthenticated
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