Local privilege escalation via heap buffer overflow
Published Feb 11, 2025 · Updated Feb 13, 2026
Heap-based buffer overflow in Microsoft Windows Core Messaging allows local users to elevate privileges on affected Windows systems. Microsoft identifies the flawed component and weakness class but has not disclosed the vulnerable function, message type, or bounds-checking error. Exploitation requires existing low-privilege local access and high-complexity conditions, and successful exploitation compromises system confidentiality, integrity, and availability.
Summary
What happened
Heap-based buffer overflow in Microsoft Windows Core Messaging allows local users to elevate privileges on affected Windows systems. Microsoft identifies the flawed component and weakness class but has not disclosed the vulnerable function, message type, or bounds-checking error. Exploitation requires existing low-privilege local access and high-complexity conditions, and successful exploitation compromises system confidentiality, integrity, and availability.
The record
- CVE
- CVE-2025-21414
- Published
- Feb 11, 2025
- Updated
- Feb 13, 2026
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-122, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 11, 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.20915
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