Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain low-priv local foothold
-
DeliveryReach MSMQ Queue Manager code path
-
ExploitSend crafted queue data
-
ExecutionTrigger heap buffer overflow
-
PersistExecute code in MSMQ service context
-
ImpactEscalate to SYSTEM control
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires the optional Message Queuing (MSMQ) feature to be installed and its Queue Manager service running - a non-default component, which sharply limits the exposed population to hosts that have explicitly enabled MSMQ. The CVSS vector is AV:L/AC:L/PR:L/UI:N, so the attacker must already have local, authenticated low-privilege code execution on the target (no remote or unauthenticated path, and no user interaction needed). Limiting factors: local access prerequisite, dependency on the non-default MSMQ feature, and the need for a pre-existing foothold; no special network configuration is involved. |
| Impact | The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8) describes a local attack requiring low privileges but no user interaction, yielding total confidentiality, integrity, and availability impact - consistent with SSVC 'Technical Impact: total.' Countervailing signals lower the real-world urgency: SSVC 'Exploitation: none' and 'Automatable: no,' plus a low EPSS score of 0.39% (31st percentile), suggest no widespread or automated exploitation to date. This is NOT in CISA KEV. The one elevating factor is that publicly available exploit code exists, which shortens the window for opportunistic post-compromise use. Net: a credible local privilege-escalation primitive suited to the second stage of an intrusion rather than an internet-facing mass-exploitation threat - prioritize patching where MSMQ is enabled, but it is not a drop-everything network emergency. Note the local vector means an attacker must already have a foothold and code execution on the host. |
| Exploit ScenarioDerived | An attacker who has already gained low-privileged local access to a Windows host with MSMQ installed - for example via a phishing-delivered user session or a compromised service account - invokes the vulnerable Queue Manager code path with crafted queue data to overflow a heap buffer. Leveraging the publicly available exploit code, they corrupt heap memory to execute code in the privileged MSMQ service context, escalating from a limited user to SYSTEM. This turns an initial low-value foothold into full control of the machine for persistence and lateral movement. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Jul 20, 2026
Local privilege escalation via heap-based buffer overflow in the Windows Message Queuing (MSMQ) Queue Manager component lets an authenticated local attacker corrupt heap memory and execute arbitrary code, gaining total control (SYSTEM-level) of the affected host. It impacts a broad range of Windows client and server builds from Windows Server 2012 through Windows 11 25H2/26H1 and Windows Server 2025. Microsoft has released patches; publicly available exploit code exists, though SSVC lists exploitation status as none and EPSS probability is low (0.39%).
Earlier versions of this analysis (1)
Local code execution in the Microsoft Message Queuing (MSMQ) Queue Manager affects a broad range of Windows client and server releases from Windows 10 1607 and Windows Server 2012 through Windows 11 26H1 and Windows Server 2025. A heap-based buffer overflow (CWE-122) lets an attacker who can reach the local MSMQ service run arbitrary code with high confidentiality, integrity, and availability impact; the CVSS 3.1 base score is 8.4 with a local attack vector but no privileges or user interaction required. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the vendor (Microsoft) has released a patch.
RemediationAI
Apply Microsoft's security update for the corresponding OS build via the MSRC advisory (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-54992); Patch available per vendor advisory, with fixed builds per version, e.g., Windows 11 24H2 at 10.0.26100.8875, Windows Server 2022 at 10.0.20348.5386, Windows Server 2025 at 10.0.26100.33158, Server 2012 R2 at 6.3.9600.23291, and Windows 10 22H2 at 10.0.19045.7548 - confirm the exact KB for your build in the update guide before deployment. As a compensating control where patching must be delayed, disable or uninstall the Message Queuing (MSMQ) Windows feature if it is not required, since the vulnerable Queue Manager only runs when MSMQ is installed; the trade-off is loss of any application that depends on MSMQ messaging. If MSMQ must remain enabled, restrict local access and limit which low-privileged users can run code on affected hosts, since exploitation requires an existing local foothold. There is no network-facing feature toggle to disable for this local-vector issue, so patching remains the definitive fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 18 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Message Queuing (MSMQ) is an optional Windows messaging service whose Queue Manager (mqsvc/mqqm) parses and manages message queues, historically a recurring source of memory-safety bugs (e.g., the 'QueueJumper' family). The root cause here is CWE-122, a heap-based buffer overflow: attacker-controlled input is written past the bounds of a heap allocation inside the Queue Manager, corrupting adjacent heap structures. Because MSMQ processing runs in a privileged service context, controlled corruption of heap metadata or object pointers can be steered into arbitrary code execution. The CPE set spans Windows 10 (1607/1809/21H2/22H2), Windows 11 (24H2/25H2/26H1), and Windows Server 2012 through 2025, including Server Core installations, indicating the vulnerable code is present across the whole modern Windows codebase wherever the MSMQ feature is installed.
Know when Windows Server 2012 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local heap overflow needing a low-privileged foothold (AV:L/PR:L), no user interaction, and code execution in the privileged MSMQ service yields total C/I/A impact.
Primary rating from Vendor (microsoft).
CVSS VectorNVD
Lifecycle Timeline
2DescriptionNVD
Heap-based buffer overflow in Windows Message Queuing Queue Manager allows an unauthorized attacker to execute code locally.
Executive ViewAI
A high-severity flaw in Windows Message Queuing allows local users with system access to seize complete control of affected servers and workstations, from Windows Server 2012 through 2025 and Windows 10/11. Publicly available exploit code exists, creating imminent risk of data exfiltration and operational disruption across organizations. Urgent patching of all affected systems is critical to prevent escalation from local access to system-level compromise.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
More in Windows Server 2012
View allWindows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX
<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi
Remote code execution in Microsoft Office 2007-2016 and Windows Vista through 10 allows attackers to execute arbitrary c
Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f
The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows
The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co
Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth
The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited
Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
Active Directory Domain Services Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.5), this vulnerabilit
EUVD-2026-44013
GHSA-4rvc-f57j-w38h
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB