Local privilege escalation via shared-resource race
Published Sep 9, 2025 · Updated Sep 9, 2025
Race condition in Windows Hyper-V on affected Windows builds allows local users with low privileges to elevate privileges on the host. Microsoft identifies improper synchronization during concurrent use of a shared Hyper-V resource but does not disclose the resource, code locus, or conflicting operations. Exploitation requires local low-privileged access and winning a difficult race; success elevates privileges on the same Windows host without user interaction.
Summary
What happened
Race condition in Windows Hyper-V on affected Windows builds allows local users with low privileges to elevate privileges on the host. Microsoft identifies improper synchronization during concurrent use of a shared Hyper-V resource but does not disclose the resource, code locus, or conflicting operations. Exploitation requires local low-privileged access and winning a difficult race; success elevates privileges on the same Windows host without user interaction.
The record
- CVE
- CVE-2025-54115
- Published
- Sep 9, 2025
- Updated
- Sep 9, 2025
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-362, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 9, 2025CVE publishedPublication date reported by the CVE source.
- Sep 9, 2025Record 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.7792
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