Is CVE-2026-50447 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-50447 being exploited in the wild.

How severe is CVE-2026-50447?

Critical severity, with a CVSS score of 9.8, published 14 July 2026.

Which products and versions are affected?

Microsoft Windows 11 < 10.0.26100.8875; Microsoft Windows 10 < 10.0.14393.9339; Microsoft Windows Server 2012 < 6.2.9200.26226.

Is there a fix for CVE-2026-50447?

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-50447 attacked?

It is attacked over the network, in an operating system.

Am I affected by CVE-2026-50447?

Check whether you run Microsoft Windows 11, Microsoft Windows 10 or Microsoft Windows Server 2012 at an affected version. 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.

CVE-2026-50447: Microsoft Windows Message Queuing heap overflow

Q: Is there a fix for CVE-2026-50447?

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.

Q: How is CVE-2026-50447 attacked?

It is attacked over the network, in an operating system.

Q: Am I affected by CVE-2026-50447?

Check whether you run Microsoft Windows 11, Microsoft Windows 10 or Microsoft Windows Server 2012 at an affected version. 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.

CVE-2026-50447 · Severity: critical · CVSS 9.8 · Published 2026-07-14

A critical vulnerability has been identified in the Windows Message Queuing (MSMQ) service, a component used for reliable communication between applications. An attacker can exploit this flaw over the network without any user interaction or login credentials to gain full control of the affected system. This could lead to complete data theft, service disruption, or the installation of malicious software across the corporate network.

Technologies: Microsoft Windows 11, Microsoft Windows 10, Microsoft Windows Server 2012. Vendors: Microsoft.

Quick answers

Is CVE-2026-50447 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-50447 being exploited in the wild.
How severe is CVE-2026-50447?: Critical severity, with a CVSS score of 9.8, published 14 July 2026.
Which products and versions are affected?: Microsoft Windows 11 < 10.0.26100.8875; Microsoft Windows 10 < 10.0.14393.9339; Microsoft Windows Server 2012 < 6.2.9200.26226.
Is there a fix for CVE-2026-50447?: 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-50447 attacked?: It is attacked over the network, in an operating system.
Am I affected by CVE-2026-50447?: Check whether you run Microsoft Windows 11, Microsoft Windows 10 or Microsoft Windows Server 2012 at an affected version. 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 heap-based buffer overflow (CWE-122) residing in the Windows Message Queuing (MSMQ) service. The flaw is exploitable over the network (TCP port 1801) without authentication or user interaction, as indicated by the CVSS vector AV:N/AC:L/PR:N/UI:N. An attacker sending a specially crafted MSMQ packet can trigger the overflow to achieve remote code execution (RCE) in the context of the service. Microsoft has released security updates to address this issue across multiple versions of Windows and Windows Server.

Affected products

Microsoft Windows 10 Version 1607 < 10.0.14393.9339
Microsoft Windows 10 Version 1809 < 10.0.17763.9020
Microsoft Windows 10 Version 21H2 < 10.0.19044.7548
Microsoft Windows 10 Version 22H2 < 10.0.19045.7548
Microsoft Windows 11 Version 24H2 < 10.0.26100.8875
Microsoft Windows Server 2012 < 6.2.9200.26226

Timeline

2026-07-14: advisory
2026-07-14: disclosed

References

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50447

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.