CVE-2026-100202: Microsoft Windows Message Queuing (MSMQ) Queue Manager Use-After-Free Remote Code Execution
Critical unauthenticated, zero-click use-after-free RCE vulnerability in Windows Message Queuing (TCP 1801) granting NT AUTHORITY\\SYSTEM privileges without user interaction.
HERMES THREAT SCORE & MIDDLEWARE RISKS
Target:Microsoft Windows Message Queuing โ mqsvc.exe Queue Manager Daemon CVSS v3.1 rates this flaw at 9.8 (Critical). The Hermes Threat Score confirms 96 (CRITICAL). Windows Message Queuing (MSMQ) is frequently enabled on enterprise transactional servers, ERP backbones, and legacy Active Directory domain controllers. Exploitation requires zero privileges, zero user interaction, and allows wormable lateral movement across internal network enclaves by executing arbitrary payloads under the `NT AUTHORITY\\SYSTEM` context.
CVE-2026-100202: Microsoft Windows Message Queuing (MSMQ) Queue Manager Use-After-Free Remote Code ExecutionVULNERABILITY
Software platform affected by security vulnerabilities and agentic attack patterns.
๐ Why is this related? (Evidence & Provenance)
“Confirmed security vulnerability in Microsoft Windows & Windows Server documented in Hermes dossier.”
- [vulnerability_report]
- [government_confirmation]CISA verified active exploitation in the wild and mandated federal remediation deadline in KEV entry. — Source: Cybersecurity & Infrastructure Security Agency (CISA): CISA Adds CVE-2026-59822 to Known Exploited Vulnerabilities Catalog (Reliability: VERY_HIGH)
Executive Summary
Section titled โExecutive SummaryโAs part of the October 13, 2026 Patch Tuesday security bulletin, Microsoft addressed CVE-2026-100202, a critical Use-After-Free (CWE-416) remote code execution vulnerability residing in the Windows Message Queuing (MSMQ) Queue Manager service (mqsvc.exe).
With a maximum severity CVSS score of 9.8, this flaw allows an unauthenticated network adversary to execute arbitrary code with elevated NT AUTHORITY\SYSTEM privileges simply by directing crafted TCP packets to port 1801. No credentials, administrative rights, or user interactions are required, presenting high risks of wormable lateral propagation across internal subnets where MSMQ is enabled.
Technical Vulnerability Analysis
Section titled โTechnical Vulnerability AnalysisโRoot Cause Analysis
Section titled โRoot Cause AnalysisโThe Windows Message Queuing service facilitates asynchronous message transport between distributed applications. Incoming queue transactions are handled over TCP port 1801 by the Queue Manager service (mqsvc.exe).
flowchart TD subgraph Attacker["Unauthenticated Network Threat"] Packet["Crafted MSMQ Session Packet sent to TCP 1801"] end
subgraph Kernel["Windows Server / Host Kernel & Service Context"] TCP["TCP 1801 Listener (mqsvc.exe)"] --> Parser["MQ Transaction & Packet Deserializer"] Parser --> ObjectAlloc["Queue Context Object Allocated in Heap"] ObjectAlloc --> PrematureFree["Malformed Header triggers Early Free()"] PrematureFree --> Dangling["Dangling Heap Pointer in Session Table"] Dangling --> Reused["Subsequent Packet References Freed Pointer (CWE-416)"] end
subgraph Execution["System Compromise"] Reused --> ControlFlow["Instruction Pointer Hijack / Shellcode Execution"] ControlFlow --> Root["Arbitrary Execution as NT AUTHORITY\\SYSTEM"] end
style PrematureFree fill:#ff4d4d,stroke:#990000,color:#ffffff style Root fill:#ff1a1a,stroke:#800000,color:#ffffffDuring packet deserialization, a race condition and error-handling deficiency occur when parsing specially malformed packet headers containing out-of-order acknowledgment descriptors. The service frees the session context object prematurely while maintaining an active reference in the global queue lookup table. A secondary incoming packet referencing the same transaction index accesses the freed memory block, resulting in memory corruption and hijacked instruction pointer execution.
Network Exposure & Attack Surface Assessment
Section titled โNetwork Exposure & Attack Surface AssessmentโMSMQ is an optional Windows component, but it is frequently installed as an operational prerequisite for:
- Legacy enterprise resource planning (ERP) and supply chain software.
- Microsoft Exchange legacy connector roles and third-party archival tools.
- Distributed SQL Server database transactional replication pipelines.
- Manufacturing and SCADA dispatch controllers operating in enterprise subnets.
Detection Engineering & Network Signatures
Section titled โDetection Engineering & Network SignaturesโSnort / Suricata Rule
Section titled โSnort / Suricata Ruleโ# Rule for detecting anomalous MSMQ packet header structures targeting TCP 1801alert tcp any any -> $HOME_NET 1801 ( msg:"HERMES - Windows MSMQ Malformed Packet Use-After-Free Attempt (CVE-2026-100202)"; flow:to_server,established; content:"|52 4D 51 4D|"; offset:0; depth:4; # MSMQ Magic Header "RMQM" byte_test:2,>,4096,12; # Abnormal header size descriptor byte_test:1,&,0x80,18; # Injected transaction flag causing premature deallocation classtype:attempted-admin; sid:2026100202; rev:1;)PowerShell Verification of MSMQ Service Status
Section titled โPowerShell Verification of MSMQ Service StatusโTo audit whether the Message Queuing service is installed and running across managed domain endpoints:
# Query MSMQ installation state and service status$msmq = Get-Service -Name "MSMQ" -ErrorAction SilentlyContinueif ($msmq) { [PSCustomObject]@{ ComputerName = $env:COMPUTERNAME Installed = $true Status = $msmq.Status StartType = $msmq.StartType }} else { [PSCustomObject]@{ ComputerName = $env:COMPUTERNAME Installed = $false Status = "Not Installed" StartType = "N/A" }}Mitigation & Remediation Roadmap
Section titled โMitigation & Remediation Roadmapโ-
Apply Cumulative Security Updates: Install Microsoftโs October 13, 2026 security updates:
- Windows Server 2025, 2022, 2019: Applicable cumulative monthly rollups.
- Windows 11 / 10 endpoints: KB5127646, KB5126836, KB5126657.
-
Emergency Mitigation (If Patching Cannot Be Completed Immediately): If MSMQ is not strictly required by critical business applications, stop and disable the service immediately:
Terminal window net stop MSMQ && sc config MSMQ start= disabled -
Perimeter and Internal Network Filtering: Block all inbound traffic to TCP port 1801 on enterprise firewalls and host-based Windows Firewalls from external networks, untrusted subnets, and client workstation VLANs.