Is CVE-2026-50687 exploited in the wild?

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

How severe is CVE-2026-50687?

High severity, with a CVSS score of 8.8, published 14 July 2026.

Which products and versions are affected?

Microsoft Windows 11 10.0.26100.0 to 10.0.26100.8875; Microsoft Windows Server 2025 10.0.26100.0 to 10.0.26100.33158.

Is there a fix for CVE-2026-50687?

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

It is attacked with local access, in an operating system.

Am I affected by CVE-2026-50687?

Check whether you run Microsoft Windows 11 or Microsoft Windows Server 2025 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-50687: Microsoft Windows Kernel use after free privilege escalation

CVE-2026-50687 · Severity: high · CVSS 8.8 · Published 2026-07-14

A security vulnerability has been identified in the Windows Kernel, the core component of the Microsoft Windows operating system. This flaw allows a user who already has basic access to a computer to gain full administrative control over the system. If exploited, an attacker could bypass security restrictions to access sensitive data, install malicious software, or disrupt business operations.

Technologies: Microsoft Windows 11, Microsoft Windows Server 2025. Vendors: Microsoft.

Quick answers

Is CVE-2026-50687 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-50687 being exploited in the wild.
How severe is CVE-2026-50687?: High severity, with a CVSS score of 8.8, published 14 July 2026.
Which products and versions are affected?: Microsoft Windows 11 10.0.26100.0 to 10.0.26100.8875; Microsoft Windows Server 2025 10.0.26100.0 to 10.0.26100.33158.
Is there a fix for CVE-2026-50687?: 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-50687 attacked?: It is attacked with local access, in an operating system.
Am I affected by CVE-2026-50687?: Check whether you run Microsoft Windows 11 or Microsoft Windows Server 2025 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 classified as a Use-After-Free (CWE-416) within the Windows Kernel. An attacker with local access and low-level privileges can exploit this flaw by triggering a condition where the kernel continues to use a memory pointer after it has been freed. Successful exploitation allows the attacker to execute code in kernel mode, leading to a full privilege escalation and a scope break (S:C). The vulnerability affects multiple versions of Windows 11 and Windows Server 2025. Microsoft has released security updates to address this issue.

Affected products

Microsoft Windows 11 Version 24H2 10.0.26100.0 to 10.0.26100.8875
Microsoft Windows 11 Version 25H2 10.0.26200.0 to 10.0.26200.8875
Microsoft Windows 11 version 26H1 10.0.28000.0 to 10.0.28000.2269
Microsoft Windows Server 2025 10.0.26100.0 to 10.0.26100.33158

Timeline

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

References

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

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