Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Obtain low-privileged local foothold
  2. Delivery
    Plant malicious symlink/junction for Search component
  3. Exploit
    Trigger privileged file operation to follow link
  4. Execution
    Redirect write/access to protected target
  5. Impact
    Escalate to SYSTEM privileges

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Symlink resolution safety
Exploitation Conditions

Requires the attacker to already possess authenticated local access (PR:L) to an affected Windows host - this is a privilege-escalation primitive, not a remote entry point. The attacker must be able to create filesystem links (symbolic links, junctions, or hardlinks) and win a race/timing window in which the Windows Search Component (which indexes files with elevated privileges) resolves the attacker-controlled link during a privileged file operation (CWE-59 link following). No user interaction by a victim is needed (UI:N). Limiting factors: exploitation is impossible without a prior local foothold, the Search/indexing service must be running and processing a location the attacker can influence, and the host must be at a build below the fixed version. SSVC Automatable=no indicates the flaw is not readily chained into automated/wormable attacks. Multi-user systems (RDS/terminal servers, shared workstations) are the most realistic targets.

Impact

This is a credible but not emergency-level priority. The CVSS 7.8 (HIGH) rating is driven entirely by local impact: AV:L/AC:L/PR:L/UI:N with total C:H/I:H/A:H impact, meaning an already-authenticated local user can gain SYSTEM-level privileges via a link-following (CWE-59) flaw in the Windows Search Component. The exploitation signals are consistent and point AWAY from widespread risk: SSVC reports Exploitation=none and Automatable=no, there is no CISA KEV listing, and no public exploit was identified at time of analysis - so this is not confirmed actively exploited. SSVC Technical Impact=total aligns with the CVSS C:H/I:H/A:H, confirming full compromise IS possible once the preconditions are met. The key mitigating factor is that this requires local, authenticated access (PR:L) as a foothold - it is not remotely exploitable and cannot be used for initial access. No EPSS score was provided in the input, so exploitation probability cannot be quantified. Net assessment: treat as a standard Patch-Tuesday elevation-of-privilege fix - important for multi-user hosts and as a post-exploitation escalation primitive, but not a drop-everything issue absent any exploitation evidence.

Exploit ScenarioDerived

A low-privileged attacker who already has local access (e.g. via phishing foothold, a compromised service account, or a shared terminal/RDS host) plants a malicious symbolic link or junction that the Windows Search Component follows while operating with elevated privileges, redirecting a privileged file operation to a target the attacker controls. This lets them overwrite or access protected files and escalate to SYSTEM. No public exploit code was identified at time of analysis, and SSVC rates exploitation as none.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.4% 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 authenticated attacker who already holds a low-privileged foothold on a Windows host win a link-following race and have the indexer perform a privileged file operation on attacker-controlled data, yielding full SYSTEM-level confidentiality, integrity, and availability impact. Affected platforms span Windows 10 (1607 through 22H2), Windows 11 (23H2 through 26H2/26H1), and Windows Server 2012 R2 through Server 2025 builds below the fixed levels documented by EUVD; exploitation requires local access (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.8) and no victim interaction. All exploitation signals are currently quiet - no public exploit code has been identified at time of analysis, CISA SSVC records Exploitation: none with Automatable: no, and a vendor patch is available, so this is a credible but not emergency-level priority.

RemediationAI

Apply the vendor update as the primary fix: patches are available per the Microsoft advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-88191, and the EUVD-listed build thresholds mark the fixed levels - 10.0.14393.9612 for Windows 10 1607/Server 2016, 10.0.17763.9376 for Windows 10 1809/Server 2019, 10.0.19044.7807 for Windows 10 21H2/22H2, 10.0.20348.5761 for Server 2022, 10.0.26100.33650 for Server 2025, 10.0.22631.7652 for Windows 11 23H2, 10.0.26100.9711 for 24H2, 10.0.26200.9711 for 25H2, 10.0.26300.9711 for 26H2, 10.0.28000.3231 for 26H1, and 6.3.9600.23470 for Server 2012 R2 (each including Server Core installs) - so verify installed build numbers rather than assuming a cumulative update covered every SKU. Where patching must be staged, prioritize hosts shared by multiple interactive users (RDS/Terminal Servers, kiosks, jump boxes) because PR:L means the threat model is a legitimate low-privileged account attacking upward, not a remote intruder. Compensating controls carry real trade-offs: stopping or disabling the Windows Search service (WSearch) removes the elevated indexer that resolves the attacker-controlled link, at the cost of degraded Start menu, Explorer, and Outlook search plus possible application-side indexing failures; tightening SeCreateSymbolicLinkPrivilege and auditing junction/hardlink creation reduces the attacker's ability to plant the link but can break developer tooling and legitimate symlink-based deployments, and because this is a race condition these controls reduce rather than eliminate exploitability. Reducing the number of accounts with interactive logon rights on high-value hosts, and monitoring for anomalous link creation in user-writable directories that the indexer traverses, are useful detective measures. Note that virtualization-based security or credential-guard style hardening does not address this bug class; the build-level fix is the only complete remediation, and no vendor workaround beyond the update is documented in the available references.

Affected VersionsENISA

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

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-59, improper link resolution before file access ('link following'), a TOCTOU-style weakness in which a privileged process resolves a pathname that an unprivileged user can swap or redirect between the check and the use. In the Windows Search indexing pipeline, the component walks directories and opens files using elevated rights; an attacker who can create a symbolic link, junction, or hardlink in a location the indexer traverses can point the resolved target at a privileged file or destination, causing the elevated Search process to read or write through the attacker-supplied link. The role of the attacker is inherently local: PR:L in the assessed vector means the attacker must already be logged on with some usable token, and the race must be won reliably enough to redirect the privileged operation, which is why SSVC rates Automatable as 'no' - the flaw is difficult to chain into wormable or scan-driven campaigns. SSVC Technical Impact is rated 'total', consistent with the vector's C:H/I:H/A:H: successful exploitation delivers SYSTEM-level control, so the failure is a full host compromise rather than an information leak. No CPE strings were supplied in the source data; affected platforms are instead enumerated by EUVD build ranges, which also serve as the fix thresholds.

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.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

Local privilege-escalation requiring an existing low-privileged account gives AV:L/PR:L/UI:N; link-following yields full SYSTEM compromise, so C:H/I:H/A:H with unchanged scope.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/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
Low
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.8

DescriptionCVE.org

Improper link resolution before file access ('link following') in Microsoft Windows Search Component allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

A high-severity local privilege-escalation flaw in the Microsoft Windows Search component affects a broad estate of Windows 10, Windows 11, and Windows Server 2012 R2 through Server 2025 systems, letting an authenticated attacker who already holds a low-privileged foothold on a host seize full SYSTEM-level control. Because any compromised endpoint or server can become a staging point for lateral movement and data theft, leadership should treat this as a systemic exposure across the Windows fleet rather than an isolated component issue. No public exploit code or active exploitation has been identified and a vendor patch is available, so remediation can proceed through the normal patch cycle instead of an emergency response.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.4%
Top 69% exploitable
Prevalence
Ubiquitous
Core Windows OS component present across all supported Windows client and server editions
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation More 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.4%
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
High
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
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.

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