Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain low-privileged local foothold
-
DeliveryPlant malicious symlink/junction
-
ExploitTrigger Windows Search file operation
-
ExecutionHijack privileged link resolution
-
ImpactExecute code as SYSTEM
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Symlink resolution safety
|
| Exploitation Conditions | Exploitation requires the attacker to already possess authenticated low-privilege local access to the target Windows host (CVSS PR:L, AV:L) - it is not remotely reachable and needs no user interaction. The attacker must be able to create filesystem symbolic links or NTFS junctions and induce the privileged Windows Search Component to follow them during a file-access operation (CWE-59), typically by exploiting a path/time-of-check-to-time-of-use link-resolution condition. Limiting factors: a pre-existing local foothold is mandatory, the attack is not automatable per CISA SSVC, and systems patched to the fixed builds (e.g., Windows 11 24H2 >=10.0.26100.9711, Server 2022 >=10.0.20348.5761) are not affected. |
| Impact | This is a genuine but second-tier priority. CVSS 7.8 (HIGH) reflects total technical impact (C:H/I:H/A:H) achievable by a low-privileged local user (AV:L/AC:L/PR:L/UI:N) - a classic privilege-escalation profile where a foothold is converted to SYSTEM via symlink/junction abuse (CWE-59, link following). However, the exploitation signals argue against emergency patching: CISA SSVC rates Exploitation as 'none' (no public exploit identified at time of analysis), Automatable as 'no' (the attacker must already have local code execution and win a link-resolution race/path condition), and only Technical Impact as 'total'. There is no KEV listing and no POC referenced. No EPSS score was provided in the input, so probabilistic exploitation likelihood cannot be factored in - state this gap explicitly. The signals are internally consistent rather than conflicting: a high-impact-but-non-remote, non-automatable local EoP. Treat it as a standard Patch-Tuesday-class local EoP - important for defense-in-depth and chaining after initial access, but not a drop-everything remote threat. |
| Exploit ScenarioDerived | An attacker who already has a low-privileged foothold on a Windows host (e.g., via phishing, a compromised service account, or an RCE in a user-mode app) plants a malicious symbolic link or junction that the Windows Search Component follows while operating at higher privilege, redirecting a file operation to a protected location. By winning the link-resolution timing, the attacker causes a privileged write/overwrite that yields SYSTEM-level code execution. No public exploit code was identified at time of analysis, and the SSVC framework marks exploitation as not automatable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Local privilege escalation in the Microsoft Windows Search component lets an attacker who already holds low-privilege authenticated access to a Windows host escalate to SYSTEM-level privileges by abusing improper symbolic-link/junction resolution (CWE-59) during a file-access operation. Affected builds span the Windows 10, Windows 11, and Windows Server families (including Server Core installations), as catalogued by ENISA EUVD-2026-100240; the flaw is rated CVSS 7.8 with high confidentiality, integrity, and availability impact, and exploitation requires no user interaction. No public exploit has been identified at time of analysis, CISA SSVC reports exploitation as none and automatable as no, and Microsoft has released vendor patches, so risk is best characterized as a genuine but second-tier priority that is fully addressed by applying the fixed builds.
RemediationAI
Apply the Microsoft security update for CVE-2026-96911 to move each host to or above its fixed build: Windows 11 24H2 to 10.0.26100.9711, 25H2 to 10.0.26200.9711, 23H2 to 10.0.22631.7652, 26H1 to 10.0.28000.3231, and 26H2 to 10.0.26300.9711; Windows 10 1607 to 10.0.14393.9612, 1809 to 10.0.17763.9376, and 21H2/22H2 to 10.0.19044.7807; and servers to 6.2.9200.26434 (Server 2012), 6.3.9600.23470 (Server 2012 R2), 10.0.14393.9612 (Server 2016), 10.0.17763.9376 (Server 2019), 10.0.20348.5761 (Server 2022), and 10.0.26100.33650 (Server 2025), including Server Core installations. Fixed builds listed by the EUVD for Windows 10 22H2 mirror the 21H2 threshold, so confirm the applicable build against the Microsoft advisory (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-96911) before treating any 19044.x host as remediated. Where immediate patching is not possible, compensating controls should target the local preconditions this exploit requires: restrict interactive logon and low-privilege local accounts on sensitive hosts (trading off legitimate shared-use scenarios), and monitor or, where feasible, use policy and Filesystem minifilter/AV tooling to detect and block creation of symbolic links and NTFS junctions in search-indexed or user-writable paths by unprivileged users (with the caveat that some legitimate developer and deployment workflows depend on reparse points). Because the attack is local and requires an existing foothold, hardening credential hygiene and reducing local admin sprawl further lowers exposure until the patched builds are deployed.
Affected VersionsENISA
Affected Packages
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 vulnerability is a link-following flaw (CWE-59: Improper Link Resolution Before File Access) in the Microsoft Windows Search indexing/index-service component. Windows Search runs with elevated privileges and performs file reads and metadata operations across user-influenced paths. When such a privileged process resolves a path without adequately validating reparse points, an attacker who can create a symbolic link or NTFS junction - and who can win a time-of-check-to-time-of-use race or control the target path - can redirect the elevated file access to an arbitrary destination. Because the operation occurs in the security context of the Search service rather than the attacker's, the redirection yields file disclosure, tampering, or overwrite of privileged locations. The CPE/version data in EUVD confirms the affected surface is the Windows OS itself rather than an add-on: Windows 10 1607 through 22H2, Windows 11 23H2 through 26H2, and Windows Server 2012 through 2025 (including Server Core variants) all carry distinct fixed build thresholds. Per the vector AV:L/AC:L/PR:L/UI:N, the primitive is local, low-complexity, requires low privileges already on the box, and needs no victim interaction; the SSVC assessment (Exploitation: none, Automatable: no, Technical Impact: total) indicates the impact is severe but neither observed in the wild nor trivially automated, which is consistent with the race/path-placement preconditions a CWE-59 exploit typically demands.
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
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local-only link-following EoP requiring an authenticated low-privilege user (AV:L/PR:L), no interaction, yielding full SYSTEM compromise (C/I/A:H).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Improper link resolution before file access ('link following') in Microsoft Windows Search Component allows an authorized attacker to elevate privileges locally.
Executive ViewAI
A flaw in the Microsoft Windows Search component allows someone who already holds a foothold on a Windows machine to elevate themselves to full SYSTEM-level control of that host, putting its data, configuration, and availability at risk. Because the affected code ships in current Windows 10, Windows 11, and Windows Server builds - including Server Core installations - the exposure footprint is effectively the entire corporate Windows estate rather than a single application or business unit. Vendor fixes are already released and no public exploit code has been identified at time of analysis, so this is best handled as a high-coverage, scheduled patching obligation rather than an emergency response.
Apply vendor patch.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
EUVD-2026-100240
GHSA-6h49-4whj-whjw
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB