CVE-2026-119963 – Windows Message Queuing Remote Code Execution Vulnerability
“One crafted packet, no password, no click: that is all it takes to turn a Message Queuing server into an attacker's launch pad.”
CVE-2026-119963 is a remote code execution flaw in Windows Message Queuing (MSMQ). A double free bug in the service lets an attacker who has no account on the system send a specially crafted packet and run code on the target. It affects a wide range of supported Windows client and server versions, and the attacker needs no credentials and no help from a user.
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 flaw is a double free (CWE-415) in the Windows Message Queuing service. When the service processes a malicious packet, it can release the same block of memory twice. That corrupts the memory manager's internal state, and a skilled attacker can shape that corruption to take control of the program's flow and execute code. The attack runs over the network, needs no privileges and no user interaction, and a successful exploit can fully compromise confidentiality, integrity and availability on the target. Attack complexity is high because specific protocol settings or configurations must be in place first.
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: Message Queuing often runs on servers that move orders, transactions and messages between business applications. Code execution on such a server hands an attacker a trusted foothold inside the network, where they can steal data, tamper with business messages, deploy ransomware or move to other systems. Because no login is required, a single exposed MSMQ endpoint could be the starting point of a full breach.
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 flaw is rated Critical, is reachable over the network, and needs neither credentials nor user action. Even though conditions must line up for an attack to work, the payoff is full code execution on Windows servers and workstations that are found in almost every organization. Message Queuing has a history of serious network-reachable bugs, so attackers are likely to study this patch. Deploy the update quickly, starting with any system where Message Queuing is enabled or reachable from untrusted networks.
Key Details
- Attack Vector
- Network
- Attack Complexity
- High
- Privileges Required
- None
- User Interaction
- None
- CWE Classification
- CWE-415