Skip to main content

Windows Search CVE-2026-83704

| EUVDEUVD-2026-99336 HIGH
Improper Link Resolution Before File Access (CWE-59)
2026-10-13 secure@microsoft.com GHSA-p464-jgw4-8255
7.8
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

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

  1. Access
    Obtain low-privileged local access
  2. Delivery
    Plant malicious symlink/junction in search path
  3. Exploit
    Windows Search follows link with elevated rights
  4. Execution
    Redirect privileged file write/delete
  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 pre-existing authenticated local access to the target host as a low-privileged user (PR:L, AV:L) and the ability to create filesystem links (symbolic links, junctions, or hard links) in a location the privileged Windows Search component processes; exploitation therefore depends on the Windows Search indexing service being present and active (default on Windows client editions). No remote network access and no user interaction (UI:N) are needed. Limiting factors: the attacker must already have a local foothold, must win or control a file-link-resolution operation performed by the higher-privileged Search process, and exploitation is not automatable per CISA SSVC, making this a post-compromise escalation step rather than an initial-access or wormable vector.

Impact

This is a locally-exploitable elevation-of-privilege flaw (CWE-59, link following) in the Windows Search component, rated CVSS 7.8. The vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N indicates an authenticated local attacker with low privileges, low attack complexity, and no user interaction can achieve full confidentiality, integrity, and availability impact (C:H/I:H/A:H) - consistent with SYSTEM-level privilege escalation. All exploitation signals point to a LOWER real-world urgency than the 7.8 base score alone suggests: CISA's SSVC decision framework reports Exploitation=none and Automatable=no, meaning no observed exploitation and no reliable mass-automation, though Technical Impact=total aligns with the complete CVSS impact metrics. The CVE is NOT on the CISA KEV list and no public proof-of-concept is referenced, so there is no public exploit identified at time of analysis. Net assessment: a genuine but routine Patch-Tuesday-class local EoP - valuable as a post-compromise privilege-escalation link in a chain, but not a drop-everything remote threat. Note a data conflict: the input Tag labels this 'Information Disclosure,' yet both the description ('elevate privileges locally') and the full C:H/I:H/A:H impact confirm this is an elevation-of-privilege issue, not mere information disclosure - the tag appears mislabeled.

Exploit ScenarioDerived

A low-privileged attacker who already has local code execution on a Windows host (e.g., via phishing or a compromised standard user account) plants a malicious symbolic link or junction that the Windows Search indexing/service process follows while operating with higher privileges. By winning the link-resolution race or redirecting a privileged file operation, the attacker causes a protected file to be written, overwritten, or deleted in a SYSTEM context, yielding full privilege escalation. No public exploit code is currently identified, and because AC:L/UI:N the technique is reliable once local access is obtained.

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 14, 2026

Local privilege escalation in Microsoft Windows Search (CWE-59, link following) allows an authenticated low-privileged local user to elevate to a higher-integrity context by manipulating filesystem links that the Windows Search indexing component resolves before accessing a file, rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation requires a pre-existing local foothold and the ability to create symbolic links, junctions, or hard links in a location processed by the privileged Search service; no user interaction or network access is needed, and CISA SSVC rates it as not automatable, making this a post-compromise escalation step rather than an initial-access or wormable vector. There is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis; Microsoft has released vendor updates, so affected systems should be patched on the normal monthly cadence rather than treated as an emergency.

RemediationAI

Primary fix: apply the Microsoft security update for CVE-2026-83704 from the MSRC update guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83704) and verify the installed build meets or exceeds the fixed thresholds - Windows 11 25H2/26H2/24H2 at 10.0.26200.9711 / 10.0.26300.9711 / 10.0.26100.9711 respectively, Windows 11 26H1 at 10.0.28000.3231, Windows 11 23H2 at 10.0.22631.7652, Windows 10 21H2/22H2 at 10.0.19044.7807, Windows 10 1809 and Windows Server 2019 at 10.0.17763.9376, Windows 10 1607 and Windows Server 2016 at 10.0.14393.9612, Windows Server 2025 at 10.0.26100.33650, Windows Server 2022 at 10.0.20348.5761, Windows Server 2012 R2 at 6.3.9600.23470, and Windows Server 2012 at 6.2.9200.26434. Because exploitation demands a local foothold first, prioritise patching on multi-user workstations, RDS/AVD session hosts, and jump servers where standards users routinely gain code execution. If the update cannot be deployed immediately, the most direct compensating control is disabling the Windows Search indexing service (WSearch) or removing the Windows Search feature on at-risk hosts - the trade-off is loss of fast file, Start menu, and Outlook search results, and it may break applications that depend on the index, so this should be scoped to high-value servers rather than fleets of user workstations. Additionally, ensure Windows Developer Mode is disabled enterprise-wide, since it grants SeCreateSymbolicLinkPrivilege to standard users and directly enables the symbolic-link variant of this attack; note that NTFS hard links created via mklink /H do not require that privilege, so this control reduces but does not eliminate the exposure to CWE-59 link-following. Finally, tighten write permissions on folders routinely indexed by the Search service (user profiles, public/shared directories, application data paths) so low-privileged users cannot plant link objects where the privileged indexer will resolve them, and monitor for unexpected link creation or file operations by SearchIndexer.exe; these are defence-in-depth measures only and do not substitute for installing the vendor patch, which is available per the Microsoft advisory.

Affected VersionsENISA

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

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 fix: 6.2.9200.26434
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_2012_server_core_installation fix: 6.2.9200.26434
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 20 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)', inside the Windows Search component - the indexing stack behind the WSearch service and SearchIndexer.exe. Because that service runs with high privilege (typically SYSTEM) while scanning, opening, and indexing user-writable directories, a mismatch between the time a path or link is resolved and the time the file is actually accessed lets a low-privileged attacker redirect the privileged operation to a target of their choosing. Classic manifestations include symbolic links, NTFS junctions, and hard links planted in an indexed folder so that the Search service follows the link and performs a file operation with elevated rights - enabling arbitrary file overwrite/read and, in the assessed worst case, full local privilege escalation to SYSTEM with high impact to confidentiality, integrity, and availability. The attack surface is inherently local: AV:L and PR:L in the CVSS vector confirm that authentication requirements are satisfied by an already-present standard user session, and UI:N means no victim interaction is required beyond the Search indexer processing the crafted location. Windows client editions ship with Search indexing enabled by default, which keeps the vulnerable code path reachable on nearly every workstation; server SKUs are affected where the indexing service is present and running.

Know when the next one hits your stack

  • 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 link-following EoP by an authenticated low-privilege user (AV:L/PR:L), no user interaction, yielding SYSTEM-level total impact (C/I/A:H); scope unchanged within the OS.

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:20 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

Microsoft Windows Search carries a high-severity local privilege escalation vulnerability (CVE-2026-83704) that could allow an authenticated low-privilege user, already present on a Windows endpoint, to gain higher-integrity access. The business concern is that a single compromised standard user account could be escalated into administrative or system-level control, amplifying data exposure, persistence, and lateral movement risk across the Windows estate. Patch available per vendor advisory, with no confirmed active exploitation and no public exploit identified at time of analysis, so remediation should be prioritized on the monthly patch cycle rather than treated as an emergency.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.4%
Top 65% exploitable
Prevalence
Ubiquitous
Windows Search ships in all modern 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

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