Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-69789 Overview
CVE-2026-69789 is a heap-based buffer overflow [CWE-122] in the Windows Reliable Multicast Transport Driver (RMCAST). The flaw allows an unauthenticated attacker on an adjacent network to execute code in the context of the vulnerable driver. Microsoft published the advisory on October 13, 2026.
The vulnerability affects the kernel-mode RMCAST driver (pgm.sys), which implements the Pragmatic General Multicast (PGM) protocol. Successful exploitation can compromise confidentiality, integrity, and availability of the target host. Attack complexity is high, but no user interaction or privileges are required.
Critical Impact
An attacker on the same logical network segment can trigger a heap overflow in a kernel driver, enabling remote code execution without authentication or user interaction.
Affected Products
- Microsoft Windows (Reliable Multicast Transport Driver — RMCAST / pgm.sys)
- Windows systems with the Message Queuing (MSMQ) Multicast feature enabled
- Refer to the Microsoft Vulnerability Advisory CVE-2026-69789 for the authoritative affected-version list
Discovery Timeline
- 2026-10-13 - CVE-2026-69789 published to the National Vulnerability Database (NVD)
- 2026-10-13 - Last updated in NVD database
Technical Details for CVE-2026-69789
Vulnerability Analysis
The vulnerability resides in the Reliable Multicast Transport Driver, a kernel-mode component that implements PGM for reliable multicast delivery. The driver mishandles the length or structure of attacker-controlled fields within an inbound multicast packet. This leads to a write beyond the bounds of a heap buffer allocated in non-paged pool.
Because the overflow occurs in kernel memory, successful corruption of adjacent pool chunks can be leveraged to execute code at ring 0. Exploitation requires the attacker to be on the same broadcast or multicast domain, which raises the attack complexity but does not require credentials. The impact scope covers confidentiality, integrity, and availability of the affected host.
Root Cause
The root cause is improper validation of size or offset fields in PGM packet data processed by RMCAST. The driver allocates a heap buffer based on one computed length and then copies attacker-supplied data using a different length, producing an out-of-bounds write classified under [CWE-122].
Attack Vector
The attack vector is adjacent network. An attacker sends crafted PGM multicast packets to a target that has RMCAST active, typically through Message Queuing with multicast binding enabled. No user interaction is required, and the attacker does not need prior authentication to the host. The specific memory layout dependencies account for the high attack complexity.
Microsoft has not published a public proof-of-concept. See the Microsoft Vulnerability Advisory CVE-2026-69789 for additional technical context.
Detection Methods for CVE-2026-69789
Indicators of Compromise
- Unexpected pgm.sys driver faults, bugchecks, or kernel pool corruption events on hosts with Message Queuing installed
- Inbound PGM traffic (IP protocol 113) from untrusted sources on local subnets where multicast messaging is not expected
- New or unusual multicast group subscriptions on servers that do not host MSMQ workloads
- Post-exploitation artifacts such as new kernel-level services, driver loads, or SYSTEM-context processes following anomalous multicast activity
Detection Strategies
- Inventory hosts with the Message Queuing feature or RMCAST driver loaded and monitor those systems for crashes and anomalous multicast traffic
- Alert on malformed or oversized PGM packets at network sensors capable of parsing IP protocol 113
- Correlate kernel bugcheck events referencing pgm.sys with recent inbound multicast traffic from the same broadcast domain
Monitoring Recommendations
- Enable Windows Event Log forwarding for System and kernel-mode driver events to a central SIEM for correlation
- Monitor pool allocation failures and nonpaged pool corruption indicators on servers running MSMQ
- Baseline normal multicast traffic per VLAN so that unexpected PGM senders are quickly surfaced
How to Mitigate CVE-2026-69789
Immediate Actions Required
- Apply the Microsoft security update referenced in the Microsoft Vulnerability Advisory CVE-2026-69789 to all affected Windows systems
- Identify every host with Message Queuing (MSMQ) installed and prioritize patching those systems first
- Where MSMQ is not required, uninstall the Message Queuing Windows feature to remove the RMCAST attack surface
Patch Information
Microsoft addresses CVE-2026-69789 through its October 2026 security update cycle. Consult the Microsoft Vulnerability Advisory CVE-2026-69789 for the authoritative list of affected builds and the corresponding KB article numbers. Install the vendor patch rather than relying on configuration workarounds alone.
Workarounds
- Block inbound traffic to IP protocol 113 (PGM) at host firewalls and network ACLs on segments that do not require multicast messaging
- Disable the Message Queuing service (MSMQ) on systems where it is not actively used
- Segment MSMQ servers onto dedicated VLANs with strict ingress controls to limit adjacent-network exposure
# Example: disable and remove MSMQ to eliminate the RMCAST attack surface
sc stop MSMQ
sc config MSMQ start= disabled
DISM /Online /Disable-Feature /FeatureName:MSMQ-Container /Remove /NoRestart
# Example: block inbound PGM (IP protocol 113) at the Windows firewall
netsh advfirewall firewall add rule name="Block PGM Inbound" ^
dir=in action=block protocol=113
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

