Local code execution via use-after-free
Published Aug 12, 2025 · Updated Feb 13, 2026
Use-after-free in Microsoft Desktop Window Manager allows local users with low privileges to execute arbitrary code on affected Windows builds. Microsoft identifies the component and memory-lifetime error but has not published the object, function, or input sequence that releases and later reuses the allocation. A local session and low privileges are required; successful exploitation runs code in the user's security context and can compromise data or interrupt the host.
Summary
What happened
Use-after-free in Microsoft Desktop Window Manager allows local users with low privileges to execute arbitrary code on affected Windows builds. Microsoft identifies the component and memory-lifetime error but has not published the object, function, or input sequence that releases and later reuses the allocation. A local session and low privileges are required; successful exploitation runs code in the user's security context and can compromise data or interrupt the host.
The record
- CVE
- CVE-2025-53152
- Published
- Aug 12, 2025
- Updated
- Feb 13, 2026
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 12, 2025CVE publishedPublication date reported by the CVE source.
- Feb 13, 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.10240.0 <10.0.10240.21100
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