Unauthenticated code execution via MSMQ use-after-free
Published Dec 10, 2024 · Updated Jun 9, 2026
Use-after-free in Microsoft Message Queuing on affected Windows builds allows remote attackers to execute code via a crafted MSMQ packet. Microsoft states that exploitation requires winning a race condition, but it has not disclosed the affected function or object whose lifetime is mishandled. The Message Queuing service must be enabled and reachable; successful exploitation executes code on the server without authentication or user interaction.
Summary
What happened
Use-after-free in Microsoft Message Queuing on affected Windows builds allows remote attackers to execute code via a crafted MSMQ packet. Microsoft states that exploitation requires winning a race condition, but it has not disclosed the affected function or object whose lifetime is mishandled. The Message Queuing service must be enabled and reachable; successful exploitation executes code on the server without authentication or user interaction.
The record
- CVE
- CVE-2024-49122
- Published
- Dec 10, 2024
- Updated
- Jun 9, 2026
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-416, CWE-362, T1190
- 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