Unauthenticated code execution via LSASS use-after-free
Published Dec 10, 2024 · Updated Jun 9, 2026
Use-after-free in Microsoft Windows LSASS allows remote attackers to execute code through a network request under race conditions. Microsoft identifies invalid reuse of freed memory and improper locking of sensitive memory, but does not disclose the affected function, object, or request format. Exploitation requires no credentials or user interaction, but it has high attack complexity and can compromise confidentiality, integrity, and availability.
Summary
What happened
Use-after-free in Microsoft Windows LSASS allows remote attackers to execute code through a network request under race conditions. Microsoft identifies invalid reuse of freed memory and improper locking of sensitive memory, but does not disclose the affected function, object, or request format. Exploitation requires no credentials or user interaction, but it has high attack complexity and can compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2024-49126
- Published
- Dec 10, 2024
- Updated
- Jun 9, 2026
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-591, CWE-416, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 10, 2024CVE publishedPublication date reported by the CVE source.
- Jun 9, 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.20857
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