Quick answers
- Is CVE-2026-119964 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119964 being exploited in the wild.
- How severe is CVE-2026-119964?
- High severity, with a CVSS score of 8.1, published 10 November 2026.
- Which products and versions are affected?
- Microsoft Windows Message Queuing.
- Is there a fix for CVE-2026-119964?
- 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-119964 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-119964?
- 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 double-free vulnerability in Windows Message Queuing allows remote code execution via network access without authentication. The flaw resides in memory management within the Message Queuing service, where improper handling of queued message objects leads to premature memory deallocation followed by reuse. An attacker can trigger this condition remotely to gain arbitrary code execution in the context of the affected service.
Affected products
- Microsoft Windows Message Queuing
Timeline
- 2026-11-10: disclosed