Quick answers
- Is CVE-2026-69579 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-69579 being exploited in the wild.
- How severe is CVE-2026-69579?
- Critical severity, with a CVSS score of 9.8, published 8 September 2026.
- Which products and versions are affected?
- Microsoft Windows Message Queuing.
- Is there a fix for CVE-2026-69579?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-69579 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-69579?
- Check whether you run Microsoft Windows Message Queuing. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A use-after-free vulnerability exists in Windows Message Queuing, a system service component responsible for message delivery and queuing functionality. The vulnerability allows an unauthenticated attacker to trigger a memory safety flaw by sending specially crafted network packets to the Message Queuing service. This results in remote code execution with system privileges, requiring only network connectivity to the affected machine. No authentication or user interaction is required to exploit this issue. A patch has been released by Microsoft to address this vulnerability.
Affected products
- Microsoft Windows Message Queuing
Timeline
- 2026-09-08: disclosed