# CVE-2026-119963: Windows Message Queuing double free remote code execution

Source: https://junglewise.ai/threats/cve-2026-119963-double-free-in-windows-message-queuing-allows-an-unauthorized  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-119963 · Severity: high · CVSS 8.1 · Published 2026-11-10

Windows Message Queuing, a Microsoft service that enables applications to communicate asynchronously across networks, contains a double free memory vulnerability. An attacker on the network can exploit this flaw to execute arbitrary code on affected systems without authentication, potentially compromising servers and endpoints that rely on message queuing functionality.

Technologies: [Microsoft Windows Message Queuing](https://junglewise.ai/threats/technologies/windows-message-queuing). Vendors: [Microsoft](https://junglewise.ai/threats/vendors/microsoft).

## Quick answers

**Is CVE-2026-119963 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-119963 being exploited in the wild.

**How severe is CVE-2026-119963?** 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-119963?** 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-119963 attacked?** It is attacked over the network, in an operating system.

**Am I affected by CVE-2026-119963?** 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 memory corruption when the same pointer is freed twice. The vulnerability can be exploited remotely without authentication, giving an attacker code execution on the affected host. The attack vector is network-based.

## Affected products

- Microsoft Windows Message Queuing

## Timeline

- 2026-11-10: advisory

## References

- [https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-119963](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-119963)

## Related threats

- [Windows Message Queuing use after free in Queue Manager](https://junglewise.ai/threats/cve-2026-119967-use-after-free-in-windows-message-queuing-queue-manager-allows)
- [Windows Message Queuing double free](https://junglewise.ai/threats/cve-2026-119964-double-free-in-windows-message-queuing-allows-an-unauthorized)
- [Windows Message Queuing improper input validation DoS](https://junglewise.ai/threats/cve-2026-119848-improper-input-validation-in-windows-message-queuing-allows-an)
- [Windows Message Queuing privilege escalation via untrusted pointer dereference](https://junglewise.ai/threats/cve-2026-119833-untrusted-pointer-dereference-in-windows-message-queuing-allows)
- [Microsoft Windows Message Queuing privilege escalation](https://junglewise.ai/threats/cve-2026-118126-use-after-free-in-windows-message-queuing-allows-an-authorized)