Quick answers
- Is CVE-2026-69645 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-69645 being exploited in the wild.
- How severe is CVE-2026-69645?
- High severity, with a CVSS score of 7, published 8 September 2026.
- Which products and versions are affected?
- Microsoft Windows Message Queuing.
- Is there a fix for CVE-2026-69645?
- 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-69645 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-69645?
- 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
This vulnerability is a use-after-free memory flaw in Windows Message Queuing that permits an authorized local attacker to elevate privileges. The attack requires local access and existing user credentials, but does not require network connectivity. An attacker exploiting this vulnerability can achieve arbitrary code execution with system-level privileges. A security update is available from Microsoft to remediate this issue.
Affected products
- Microsoft Windows Message Queuing
Timeline
- 2026-09-08: disclosed