Loading vulnerability…
CVE-2026-54992 is a high-severity heap-based buffer overflow in the Windows Message Queuing Queue Manager. The flaw arises from improper handling of memory on the heap and can lead to memory corruption during processing within the Queue Manager component. Microsoft classifies the issue as a remote code execution vulnerability, but the available exploitation path is local rather than network-reachable. Successful exploitation allows an unauthorized attacker to execute arbitrary code on the affected system. The vulnerability affects multiple supported Windows client and server releases, including Server Core installations.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A heap-based buffer overflow in Windows Message Queuing Queue Manager that allows local code execution by an unauthorized attacker. It is significant due to its high CVSS 3.1 score of 8.4 and broad impact across multiple Windows client and server versions.
A heap-based buffer overflow remote code execution vulnerability in Microsoft Message Queuing Queue Manager.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.