Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Obtain low-privilege local foothold
  2. Delivery
    Interact with Windows Search component
  3. Exploit
    Trigger use-after-free (CWE-416)
  4. Execution
    Corrupt freed object memory
  5. Persist
    Hijack execution flow
  6. Impact
    Elevate to SYSTEM privileges

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

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

Exploitation Conditions

Exploitation requires local access to an affected Windows host AND an existing low-privilege authenticated context (PR:L) from which the attacker can invoke the Windows Search indexing/query component to trigger the use-after-free; no user interaction is required (UI:N). The Windows Search component is present and enabled by default across supported Windows client and server builds, so no non-default configuration is needed to reach the vulnerable code. The key limiting factor is that the attacker cannot reach this flaw remotely or unauthenticated - they must first gain code execution or an interactive/standard user session on the target (via phishing, stolen credentials, a sandboxed process, or chaining from another bug), which confines it to a post-foothold privilege-escalation step on the specific builds listed below the fixed versions in EUVD-2026-100108.

Impact

This is a credible but not emergency-level priority. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8 HIGH) describes a local privilege-escalation flaw: the attacker must already have low-privilege authenticated access to the host (PR:L), execution is local (AV:L), low complexity (AC:L), and no user interaction is needed. CWE-416 (use-after-free) in the Windows Search component matches the C:H/I:H/A:H total technical impact, consistent with the SSVC 'Technical Impact: total' rating. However, multiple signals point toward LOW immediate urgency: SSVC 'Exploitation: none' indicates no observed exploitation, 'Automatable: no' indicates it cannot be reliably mass-exploited (typical of memory-corruption EoP requiring a prior foothold), there is no CISA KEV listing, and no public exploit or POC is referenced in the provided data. EPSS score was NOT provided in the input, so exploitation probability cannot be quantified here. The high base score is driven by impact, not by ease of remote reach - this is a post-compromise escalation primitive, not an internet-facing entry point. Priority should be standard Patch-Tuesday cadence, elevated on multi-user or shared hosts where low-privilege users are untrusted.

Exploit ScenarioDerived

An attacker who already holds a low-privileged foothold on a Windows system (e.g., a standard user account, a sandboxed process, or post-phishing code execution) locally triggers the use-after-free condition in the Windows Search component to corrupt memory and hijack execution flow, elevating to SYSTEM. No public exploit code is identified at time of analysis, and SSVC records no observed exploitation. Because AV:L and PR:L are required, this is a second-stage escalation step rather than an initial access vector.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% 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, low-privileged user on an affected Windows host trigger a use-after-free in the search indexing/query path and escalate to higher-integrity code execution, with high impact across confidentiality, integrity, and availability (CVSS 7.8, AV:L/PR:L/UI:N). Because Windows Search is present and enabled by default on every supported client and server build listed in EUVD-2026-100108, no non-default configuration is required - the only prerequisite is an existing standard user session or foothold on the target, making this a post-exploitation escalation step rather than a remotely reachable flaw. Neither CISA KEV nor the SSVC assessment indicates active exploitation (Exploitation: none), and no public exploit code has been identified at time of analysis, so this is a credible but not emergency-level priority that should be closed through routine monthly patching.

RemediationAI

Vendor-released patch: Microsoft has published fixes for all affected branches, and the primary remediation is to install the current cumulative update for each build so that the OS reaches or exceeds the fixed build numbers - Windows 11 23H2 to 10.0.22631.7652, 24H2 to 10.0.26100.9711, 25H2 to 10.0.26200.9711, 26H1 to 10.0.28000.3231, and 26H2 to 10.0.26300.9711; Windows 10 21H2/22H2 to 10.0.19044.7807, 1809 to 10.0.17763.9376, and 1607 to 10.0.14393.9612; Windows Server 2012 R2 to 6.3.9600.23470, Server 2016 to 10.0.14393.9612, Server 2019 to 10.0.17763.9376, Server 2022 to 10.0.20348.5761, and Server 2025 to 10.0.26100.33650 - and the advisory must be tracked at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-88182 for any revised build numbers, since apply-order and supersedence rules for cumulative updates matter on Windows. Because exploitation requires an existing local authenticated session, the practical compensating controls are host-hardening measures that raise the cost of the prerequisite foothold rather than true mitigations of the flaw itself: enforce least privilege so users operate as standard accounts and cannot freely spawn local code, apply application allowlisting to block untrusted binaries from running in user sessions, and monitor for anomalous child processes or token-elevation behaviour originating from SearchIndexer.exe or the WSearch service. Disabling the Windows Search service (WSearch) is sometimes suggested but carries meaningful trade-offs - it breaks Start menu, File Explorer and Outlook search and indexing, is difficult to remove cleanly on modern Windows builds, and may not eliminate every path into the vulnerable component, so it should be treated as a last-resort measure on high-value hosts rather than a general fix. No exploitation activity is confirmed (SSVC Exploitation: none) and no public exploit code is identified, so remediation can proceed on a normal patch cadence without emergency change control.

Affected VersionsENISA

Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
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
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33650
Windows Server 2016 10.0.14393.0 <10.0.14393.9612
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9376
Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711
Windows Server 2025 10.0.26100.0 <10.0.26100.33650
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 11 Version 23H2 10.0.22631.0 <10.0.22631.7652
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23470
Windows Server 2019 10.0.17763.0 <10.0.17763.9376
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 Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23470
Windows 10 Version 21H2 10.0.19044.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 vulnerability is a use-after-free (CWE-416) in the Windows Search component, the indexing and query subsystem built around the WSearch service and SearchIndexer.exe that maintains the Windows Search index consumed by Start menu search, File Explorer, Outlook and other applications. In a use-after-free, an object on the heap is released while a stale pointer to it is still retained; a subsequent operation dereferences that dangling pointer, and if the freed memory has been reallocated with attacker-influenced content, the corrupted object can be used to redirect control flow or corrupt adjacent structures. That maps directly to the impact triad of the assessed vector: total loss of confidentiality, integrity, and availability (C:H/I:H/A:H) if the corruption is successfully shaped into code execution in the context of the search service, which runs at a high privilege level. The vector AV:L/AC:L/PR:L/UI:N/S:U confirms the attack surface is local and low-complexity but gated behind an existing low-privilege authenticated context - the attacker must already be able to invoke the vulnerable indexing/query functionality from a standard user session, whether obtained interactively, through a sandboxed process, or by chaining another bug. The DoS and Memory Corruption tags in the source data are consistent with the CWE-416 root cause and do not indicate a separate remote vector.

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 use-after-free EoP requiring an existing low-privilege session (AV:L, PR:L), low complexity and no user interaction, yielding full SYSTEM-level confidentiality, integrity and availability impact (C/I/A:H).

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

Use after free in Microsoft Windows Search Component allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

A high-severity local privilege-escalation vulnerability in Microsoft Windows Search could let an authenticated standard user on an affected Windows client or server gain higher-integrity code execution, compromising the confidentiality, integrity, and availability of that host. Because Windows Search is enabled by default on the affected builds, any existing low-privileged foothold-such as a compromised standard user account or malware running in user context-can be leveraged to expand access across the system. No active exploitation or public exploit has been identified at time of analysis, so leadership should treat this as a routine but important patching priority rather than an emergency.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 77% exploitable
Prevalence
Ubiquitous
core component of Microsoft Windows, present on nearly all deployments
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.3%
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

Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

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