Is CVE-2026-50679 exploited in the wild?

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

How severe is CVE-2026-50679?

High severity, with a CVSS score of 7.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-50679?

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

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

Am I affected by CVE-2026-50679?

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-50679: Microsoft Windows Search Component heap overflow privilege escalation

CVE-2026-50679 · Severity: high · CVSS 7.8 · Published 2026-07-14

A security vulnerability has been identified in the Microsoft Windows Search Component, which is responsible for indexing and searching files on the operating system. An attacker who already has basic access to a computer could exploit this flaw to gain full administrative control over the system. This could allow them to view sensitive data, install malicious software, or disrupt business operations.

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

Quick answers

Is CVE-2026-50679 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-50679 being exploited in the wild.
How severe is CVE-2026-50679?: High severity, with a CVSS score of 7.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-50679?: 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-50679 attacked?: It is attacked with local access, in an operating system.
Am I affected by CVE-2026-50679?: 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

A heap-based buffer overflow vulnerability (CWE-122) exists in the Microsoft Windows Search Component. The flaw is triggered when the component improperly handles memory allocation during search operations. An attacker with low-privileged local access can exploit this by running a specially crafted application to overwrite adjacent memory, leading to arbitrary code execution with SYSTEM privileges. 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: Initial publication by Microsoft and NVD
2026-07-14: advisory

References

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

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