Skip to main content

Windows Search CVE-2026-88160

| EUVDEUVD-2026-99590 HIGH
Race Condition (CWE-362)
2026-10-13 secure@microsoft.com GHSA-wqcc-xcwx-rfpc
7.0
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privileged local user
  2. Delivery
    Repeatedly invoke Windows Search operation
  3. Exploit
    Win race window on shared resource
  4. Execution
    Corrupt synchronization state
  5. Impact
    Elevate to SYSTEM privileges

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Concurrency control, locking
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires the attacker to already hold valid low-privileged local credentials on the target host (PR:L, AV:L) and to interact with the Windows Search Component to reach the vulnerable shared resource. Exploitation is limited by high attack complexity (AC:H): the attacker must reliably win a narrow race-condition timing window on the improperly synchronized resource, which typically demands many repeated attempts and favorable scheduling conditions. No remote or unauthenticated path exists, and no special non-default Search configuration is indicated in the available data - the component is present by default in all supported Windows editions.

Impact

This is a credible but not top-tier priority. The CVSS 3.1 vector (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.0 HIGH) describes a local elevation-of-privilege flaw requiring an already-authenticated low-privileged user and a high-complexity race window, yet yielding full confidentiality, integrity, and availability impact (typically SYSTEM). No EPSS score, no CISA KEV listing, and no public POC were provided, so exploitation status is 'no public exploit identified at time of analysis.' The AC:H metric is significant: winning a race condition reliably is non-trivial, which tempers real-world weaponization despite the complete impact triple. No SSVC decision data was supplied. The key tension is between the CRITICAL-sounding C:H/I:H/A:H and the practical barriers (local access + hard-to-win race) - treat this as a privilege-escalation building block for post-compromise chains rather than an internet-facing emergency. The 'Information Disclosure' tag conflicts with the description and CWE-362, which describe privilege elevation; verify categorization with the MSRC advisory.

Exploit ScenarioDerived

An attacker who already has a standard user foothold on a Windows host (via phishing, stolen credentials, or a prior low-privilege compromise) repeatedly triggers the Windows Search Component to hit a narrow timing window in an improperly synchronized shared resource. By winning the race, they manipulate the shared state to execute code or gain access at SYSTEM level, escalating from limited user to full host control. No public exploit code was identified, and the high attack complexity means exploitation requires repeated, timing-sensitive attempts.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 13, 2026

Local privilege escalation in the Microsoft Windows Search Component lets an attacker who already holds low-privileged credentials on the host race an improperly synchronized shared resource to elevate into a higher-integrity context, gaining read and write access to protected data and the ability to impair system integrity. Exploitation is constrained by high attack complexity (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) - the attacker must reliably win a narrow timing window through repeated attempts - and no remote or unauthenticated path exists because the Search component is present by default in all supported Windows editions. There is no public exploit code and no confirmed active exploitation (no public exploit identified at time of analysis), and Microsoft has released a fix, so this is best treated as a credible but not top-tier patching priority.

RemediationAI

Vendor-released patch: the fix is available from Microsoft - apply the current cumulative security update for each affected build (the EUVD thresholds imply fixed levels of 10.0.14393.9612 for 1607/Server 2016, 10.0.17763.9376 for 1809/Server 2019, 10.0.19044.7807 for Windows 10 21H2/22H2, 6.3.9600.23470 for Server 2012 R2, 10.0.20348.5761 for Server 2022, 10.0.26100.33650 for Server 2025 and the corresponding 10.0.22631.7652 / 10.0.26100.9711 / 10.0.26200.9711 / 10.0.28000.3231 / 10.0.26300.9711 builds for Windows 11 23H2 through 26H2) via Windows Update, WSUS, or the Microsoft Update Catalog, per https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-88160. Because exploitation is local-only and requires pre-existing low-privileged credentials, the highest-value compensating control is attack-surface reduction on multi-user and Remote Desktop hosts: audit and remove unnecessary local accounts and interactive/RDP logon rights so that only trusted users can log on locally, accepting the operational cost of tighter access management. Reducing the number of concurrent interactive sessions limits the scheduler contention a race attempt needs, but it is an unproven mitigation and degrades legitimate multi-session workloads. Disabling the Windows Search service (WSearch) to remove the vulnerable shared resource is technically possible, but it breaks Start menu and File Explorer search, Outlook and mailbox indexing, and search-backed features in many line-of-business applications, and it is not a supported security control - treat it as a last resort for isolated, high-risk hosts only. Detection should focus on anomalous Search indexer process behavior and unexpected token/integrity-level changes by non-administrative users. Since no public exploit exists and high attack complexity limits reliability, patching can follow the standard monthly cycle rather than an emergency out-of-band deployment.

Affected VersionsENISA

Windows Server 2022 10.0.20348.0 <10.0.20348.5761
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9612
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9376
Windows Server 2019 10.0.17763.0 <10.0.17763.9376
Windows Server 2025 10.0.26100.0 <10.0.26100.33650
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23470
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7807
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.3231
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7652
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33650
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23470
Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows Server 2016 10.0.14393.0 <10.0.14393.9612
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9612
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9376
Windows 10 Version 22H2 10.0.19045.0 <10.0.19044.7807

Affected Packages

euvd windows_10_version_1607 fix: 10.0.14393.9612
euvd windows_10_version_1809 fix: 10.0.17763.9376
euvd windows_10_version_21h2 fix: 10.0.19044.7807
euvd windows_10_version_22h2 fix: 10.0.19044.7807
euvd windows_11_version_23h2 fix: 10.0.22631.7652
euvd windows_11_version_24h2 fix: 10.0.26100.9711
euvd windows_11_version_25h2 fix: 10.0.26200.9711
euvd windows_11_version_26h1 fix: 10.0.28000.3231
euvd windows_11_version_26h2 fix: 10.0.26300.9711
euvd windows_server_2012_r2 fix: 6.3.9600.23470
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23470
euvd windows_server_2016 fix: 10.0.14393.9612
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9612
euvd windows_server_2019 fix: 10.0.17763.9376
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9376
euvd windows_server_2022 fix: 10.0.20348.5761
euvd windows_server_2025 fix: 10.0.26100.33650
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33650

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 18 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-362, Concurrent Execution using Shared Resource with Improper Synchronization ('race condition'), in the Windows Search indexing component. Two or more execution contexts reach the same shared resource without adequate locking or ordering, so an attacker who can schedule operations against that resource can interleave them to produce a state the component does not expect - in this case, an operation performed in a more privileged context than the attacker's own. The assessed vector (AV:L/PR:L/AC:H) confirms the vulnerable surface is reachable only from the local host by a principal that already holds valid low-privileged credentials; the high complexity reflects the fact that the race window is narrow and winning it generally requires many repeated attempts and favorable scheduling. The Windows Search stack operates behind a service/integrity boundary that is more privileged than a standard user, which is what makes a successful race potentially privilege-elevating rather than merely a crash. Note that the supplied tags include 'Information Disclosure' while the CVSS metrics indicate high confidentiality, integrity and availability impact with unchanged scope; the Microsoft Security Update Guide entry for CVE-2026-88160 is the authoritative source for the precise affected code path and impact statement. This issue is tracked in the EU as EUVD-2026-99590.

Know when Windows gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (microsoft) PRIMARY 7.0 HIGH
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.0 HIGH

Local authenticated standard user (AV:L/PR:L), race condition makes it AC:H, no UI needed, and successful win yields full SYSTEM-level C/I/A impact within an unchanged scope.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Local
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Oct 13, 2026 - 20:20 EUVD
CVE Published
Oct 13, 2026 - 19:21 cve.org
HIGH 7.0

DescriptionCVE.org

Concurrent execution using shared resource with improper synchronization ('race condition') in Microsoft Windows Search Component allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

Microsoft Windows Search Component contains a high-severity local privilege escalation vulnerability (CVE-2026-88160) that could allow an authenticated local attacker with low privileges to gain higher-integrity access, read or modify protected data, and impair system integrity. There is no public exploit identified at time of analysis, and exploitation requires local access and high attack complexity, so the immediate organizational risk is greatest where attackers or insider threats already have a foothold on endpoints or servers. Leadership should ensure patching is managed alongside other high-severity Windows updates, with priority for regulated, high-value, or sensitive-data systems.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 96% exploitable
Prevalence
Ubiquitous
Windows Search ships in all supported Windows client and server editions
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
Medium
Technical Impact
Total

Priority Score

35
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +35
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Race conditions occur when multiple concurrent requests exploit the brief time gap between checking a condition and acting upon it (TOCTOU - Time of Check, Time of Use).

CVE-2025-52691 CRITICAL POC
10.0 Dec 29

Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio

CVE-2019-0803 HIGH POC
7.8 Apr 09

Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in

CVE-2020-1472 MEDIUM POC
5.5 Aug 17

A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr

CVE-2025-33053 HIGH POC
8.8 Jun 10

Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables

CVE-2025-33073 HIGH POC
8.8 Jun 10

Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker

CVE-2025-13315 CRITICAL POC
9.3 Nov 19

Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b

CVE-2013-10047 CRITICAL POC
9.3 Aug 01

An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote

CVE-2012-10030 CRITICAL POC
9.3 Aug 05

FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit

CVE-2025-34101 CRITICAL POC
9.3 Jul 10

Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio

CVE-2025-13316 HIGH POC
8.2 Nov 19

Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred

CVE-2025-34095 CRITICAL POC
9.3 Jul 10

Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/

CVE-2025-11953 CRITICAL POC
9.8 Nov 03

React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy