CVE-2026-50373 Overview
CVE-2026-50373 is an improper access control vulnerability [CWE-284] in the Microsoft Windows Search Component. An authenticated local attacker can leverage the flaw to elevate privileges on affected Windows client and server systems. Microsoft published the advisory on July 14, 2026, and the issue affects a broad set of supported Windows 10, Windows 11, and Windows Server releases.
Exploitation requires local access and low privileges but no user interaction. Successful exploitation yields high impact to confidentiality, integrity, and availability, typically resulting in SYSTEM-level code execution through the Windows Search service context.
Critical Impact
A low-privileged local user can elevate to SYSTEM through the Windows Search Component, gaining full control of the host and enabling post-compromise actions such as credential theft, persistence, and lateral movement.
Affected Products
- Microsoft Windows 10 (1809, 21H2, 22H2) across x86, x64, and ARM64 architectures
- Microsoft Windows 11 (24H2, 25H2, 26H1) across x64 and ARM64 architectures
- Microsoft Windows Server 2019, Windows Server 2022, and Windows Server 2025
Discovery Timeline
- 2026-07-14 - CVE-2026-50373 published to NVD and Microsoft releases security update
- 2026-07-20 - Last updated in NVD database
Technical Details for CVE-2026-50373
Vulnerability Analysis
The vulnerability resides in the Windows Search Component, a system service that indexes files, email, and other content across the operating system. The service runs with elevated privileges and interacts with numerous user-writable locations, making access control enforcement critical.
Improper access control [CWE-284] within this component allows an authenticated local user to perform operations that should be restricted to higher-privileged principals. The attack complexity is low, and no user interaction is required. Successful exploitation results in privilege escalation to SYSTEM.
The EPSS score at publication was approximately 0.284%, reflecting a low near-term likelihood of mass exploitation. However, local privilege escalation flaws in core Windows components are routinely incorporated into post-exploitation toolkits once technical details become public.
Root Cause
According to Microsoft's advisory, the root cause is improper access control within the Windows Search Component. Access checks on protected objects, handles, or interfaces exposed by the search service are insufficient, allowing a standard user to influence resources that should be reserved for privileged callers. Microsoft has not published low-level technical detail beyond the CWE-284 classification.
Attack Vector
An attacker must first obtain code execution on the target as an authenticated user, for example through phishing, a compromised application, or valid credentials. The attacker then interacts with the Windows Search service to abuse the missing or insufficient access check and gain SYSTEM privileges. Because the attack is local and requires authentication, it is most commonly chained with an initial access technique in a broader intrusion.
No public proof-of-concept code or exploit-in-the-wild reports are available at this time. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog.
Detection Methods for CVE-2026-50373
Indicators of Compromise
- Unexpected child processes spawned by SearchIndexer.exe, SearchProtocolHost.exe, or SearchFilterHost.exe running as NT AUTHORITY\SYSTEM
- New services, scheduled tasks, or registry Run keys created immediately after Windows Search activity by a standard user session
- Anomalous file writes by the Windows Search service into user-writable directories followed by execution of those files
Detection Strategies
- Hunt for standard-user processes interacting with Windows Search named pipes, COM interfaces, or RPC endpoints followed by privilege transitions
- Alert on token elevation events (Windows Event ID 4672) tied to processes originally launched under a non-privileged user context
- Correlate Sysmon Event ID 1 (process creation) with Event ID 10 (process access) targeting SearchIndexer.exe from non-administrative accounts
Monitoring Recommendations
- Enable and forward Sysmon, PowerShell, and Windows security event logs to a centralized analytics platform for behavioral correlation
- Monitor changes to ACLs, service configurations, and registry keys under HKLM\SOFTWARE\Microsoft\Windows Search
- Baseline normal Windows Search process behavior on servers and endpoints to surface deviations quickly
How to Mitigate CVE-2026-50373
Immediate Actions Required
- Apply the July 2026 Microsoft security update referenced in the Microsoft Security Update Guide for CVE-2026-50373 to all affected Windows 10, Windows 11, and Windows Server systems
- Prioritize patching of multi-user systems, terminal servers, and jump hosts where local users are more likely to exist
- Audit local and domain accounts to remove unnecessary interactive logon rights on sensitive systems
Patch Information
Microsoft has released cumulative security updates that address CVE-2026-50373 for all listed supported versions. Refer to the Microsoft Security Update for CVE-2026-50373 advisory for the specific KB article numbers per Windows release and deploy through Windows Update, WSUS, Microsoft Intune, or your standard patch management pipeline.
Workarounds
- No official workarounds have been published by Microsoft; patch installation is the recommended remediation
- Where patching is delayed, restrict interactive and remote logon rights so that only trusted administrators can execute code locally on affected hosts
- Apply application control policies such as Windows Defender Application Control or AppLocker to limit which binaries standard users can launch
# Verify installed updates and confirm the CVE-2026-50373 patch is present
Get-HotFix | Sort-Object -Property InstalledOn -Descending | Select-Object -First 20
# Query Windows Search service state and configuration
sc.exe qc WSearch
Get-Service -Name WSearch | Format-List *
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

