Local privilege escalation via camsvc race condition
Published Sep 9, 2025 · Updated Sep 9, 2025
A race condition in Microsoft Windows camsvc allows local users on affected builds to elevate privileges and compromise the system. Microsoft identifies concurrent access to a shared resource and a resulting use-after-free in camsvc, but has not disclosed the affected code path or raced operations. A low-privilege local account and successful race timing are required; exploitation grants elevated control over confidentiality, integrity, and availability.
Summary
What happened
A race condition in Microsoft Windows camsvc allows local users on affected builds to elevate privileges and compromise the system. Microsoft identifies concurrent access to a shared resource and a resulting use-after-free in camsvc, but has not disclosed the affected code path or raced operations. A low-privilege local account and successful race timing are required; exploitation grants elevated control over confidentiality, integrity, and availability.
The record
- CVE
- CVE-2025-54108
- Published
- Sep 9, 2025
- Updated
- Sep 9, 2025
- Vendor
- Microsoft
- Product
- Windows Server 2025 (Server Core installation)
- Classifications
- CWE-416, 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.26100.0 <10.0.26100.6584
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