Local privilege escalation via attacker-controlled file path
Published Mar 10, 2026 · Updated Mar 10, 2026
External path control in the Microsoft Windows Kernel allows local users with low privileges to elevate privileges on affected systems. Microsoft identifies CWE-73 but has not disclosed the kernel routine, attacker-controlled path source, or privileged file operation that causes the flaw. A local authenticated foothold is required; successful exploitation grants control over system confidentiality, integrity, and availability.
Summary
What happened
External path control in the Microsoft Windows Kernel allows local users with low privileges to elevate privileges on affected systems. Microsoft identifies CWE-73 but has not disclosed the kernel routine, attacker-controlled path source, or privileged file operation that causes the flaw. A local authenticated foothold is required; successful exploitation grants control over system confidentiality, integrity, and availability.
The record
- CVE
- CVE-2026-24287
- Published
- Mar 10, 2026
- Updated
- Mar 10, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-73, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 10, 2026CVE publishedPublication date reported by the CVE source.
- Mar 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=10.0.17763.0 <10.0.17763.8511
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