CVE-2026-119964 – Windows Message Queuing Remote Code Execution Vulnerability
“When a message service can be tricked into freeing the same memory twice, an attacker gets a free pass to run code on your servers.”
CVE-2026-119964 is another remote code execution flaw in Windows Message Queuing (MSMQ). A double free bug lets an unauthenticated attacker send a specially crafted packet over the network and execute code on the target system. It affects nearly every supported version of Windows client and server, and it needs no credentials and no user interaction.
CVSS Score: 8.1
SEVERITY: Critical
THREAT: An unauthenticated attacker anywhere on the network could send crafted packets to a Windows system running Message Queuing and run their own code on it. No login and no user click are needed.
EXPLOITS: This vulnerability is not known to be exploited in the wild. It was not publicly disclosed before the fix, and no public proof-of-concept code is known.
TECHNICAL SUMMARY: The root cause is a double free (CWE-415) in the Message Queuing service. While handling a malicious packet, the service frees the same memory more than once. This leaves memory in a corrupted state that an attacker can abuse to redirect execution and run code. The attack runs over the network, needs no privileges and no user interaction, and success means full impact to confidentiality, integrity and availability. Attack complexity is high, because particular protocol settings or configurations must be in place before the attack can succeed.
EXPLOITABILITY: Affected versions include Windows 10 (versions 1607, 1809, 21H2 and 22H2), Windows 11 (versions 23H2, 24H2, 25H2, 26H1 and 26H2), and Windows Server 2016, 2019, 2022 and 2025, including Server Core installations. An attacker sends a specially crafted packet to the Message Queuing service over the network. The attack only works when specific conditions, such as particular protocol settings or configurations, are in place, which makes it harder to pull off at scale.
BUSINESS IMPACT: Many line-of-business applications depend on Message Queuing to pass orders, payments and system events between servers. If an attacker gains code execution on one of these servers, they can read or alter sensitive business messages, disrupt critical workflows, plant ransomware, and use the server as a stepping stone into the rest of the network. The lack of any login requirement makes exposed MSMQ systems an easy first target.
WORKAROUND: No official mitigations or workarounds are listed. If you cannot patch right away, disable the Message Queuing service on systems that do not need it, and block inbound traffic to the Message Queuing port (TCP 1801) at the host and network firewall so only trusted systems can reach it.
URGENCY: This vulnerability is rated Critical, can be reached over the network, and requires no account or user action. It ships alongside a sister flaw in the same service, which doubles the attention attackers will give to Message Queuing this month. The high attack complexity slows attackers down but does not stop them. Roll out the update promptly, and treat any server with Message Queuing enabled as a top priority.
Key Details
- Attack Vector
- Network
- Attack Complexity
- High
- Privileges Required
- None
- User Interaction
- None
- CWE Classification
- CWE-415