Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local code execution
-
DeliveryTrigger use-after-free in Windows Search component
-
ExploitReclaim freed object with attacker-controlled data
-
ExecutionHijack execution in privileged context
-
ImpactGain SYSTEM-level 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 | The attacker must already possess local, authenticated low-privileged access to the target Windows host (PR:L, AV:L) and be able to run code that exercises the Windows Search Component (the Windows Search indexing/query service, which is enabled by default on client Windows and present across the listed Server SKUs). No user interaction is required (UI:N) and attack complexity is low (AC:L), so once local code executes, no special non-default configuration is needed. The primary limiting factor is the local-access prerequisite: this cannot be exploited remotely or by an unauthenticated attacker, making it a post-compromise privilege-escalation primitive rather than an initial-access vector. Affected builds are those below the fixed versions listed in EUVD (e.g., Windows 11 24H2 below 10.0.26100.9711, Server 2025 below 10.0.26100.33650); patched builds remove the condition. |
| Impact | This is a credible patch-priority item but not an emergency. The CVSS 3.1 vector (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8) describes a local privilege-escalation path: the attacker must already have local, low-privileged code execution (PR:L, AV:L), but complexity is low (AC:L) and no user interaction is needed (UI:N), with full confidentiality, integrity and availability impact on the host. No EPSS score, KEV entry, or public PoC was provided in the input, so the exploitation signal is: no public exploit identified at time of analysis - not CISA KEV and not independently confirmed as exploited. Use-after-free kernel/component EoP bugs in Windows historically become reliable exploitation targets and are frequently chained after initial access, so the latent risk is higher than the absence of a PoC suggests, but there is no evidence of in-the-wild use here. Conflicting/missing signals to note explicitly: EPSS and PoC status are absent from the input (cannot confirm either way), and the input Tags include 'Denial Of Service' which is only partially consistent with a full C:H/I:H/A:H elevation-of-privilege UAF - treat the DoS label as a secondary/possible outcome rather than the primary impact. Net: a real but routine high-severity local EoP to patch on the normal expedited Windows cadence, not a drop-everything network-exploitable issue. |
| Exploit ScenarioDerived | An attacker who already has a low-privileged foothold on a Windows host (e.g., via a standard user account, a compromised service, or a malware dropper) runs code that triggers the use-after-free in the Windows Search component to corrupt memory and hijack execution in a higher-privileged context. Because the CVSS vector is local (AV:L) with low attack complexity and no user interaction, exploitation is deterministic once code runs on the box, but it cannot be launched remotely without prior access. No public exploit was identified in the provided data, so weaponization effort is unknown. |
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 allows an authenticated attacker who already holds low-privileged code execution on a Windows host to abuse a use-after-free and elevate to higher integrity, with the CVSS vector (AV:L/AC:L/PR:L/UI:N, 7.8, C/I/A all High) confirming that the local-access and authenticated prerequisites are the only real barriers. Exploitation requires no user interaction and no non-default configuration, making this a useful post-compromise escalation primitive rather than an initial-access vector. Microsoft has released vendor patches and no public exploit identified at time of analysis, and there is no KEV listing, so this is best treated as a high-priority patch item rather than an emergency.
RemediationAI
Vendor-released patches are available per the Microsoft MSRC update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-96324; apply the update that moves each host to or above its fixed build, for example 10.0.26100.9711 for Windows 11 24H2, 10.0.26200.9711 for Windows 11 25H2, 10.0.28000.3231 for Windows 11 26H1, 10.0.26300.9711 for Windows 11 26H2, 10.0.22631.7652 for Windows 11 23H2, 10.0.19044.7807 for Windows 10 21H2/22H2, 10.0.14393.9612 for Windows 10 1607 and Windows Server 2016, 10.0.17763.9376 for Windows 10 1809 and Windows Server 2019, 10.0.20348.5761 for Windows Server 2022, 10.0.26100.33650 for Windows Server 2025, 6.2.9200.26434 for Windows Server 2012, and 6.3.9600.23470 for Windows Server 2012 R2, including the Server Core installations of each. Because the assessed vector is AV:L/PR:L, patching is the definitive fix and the practical interim controls target the local-access prerequisite rather than the bug itself: on hosts that do not require search (many server roles and hardened client images), stop and disable the Windows Search service (WSearch) and, where feasible, remove or disable the search feature via Optional Features - the trade-off is loss of Start menu, File Explorer, Outlook and other indexed search functionality, which can break workflows and should be validated before broad rollout; alternatively, tighten who can obtain an interactive or service local logon on exposed hosts so that low-privileged code cannot reach the component, accepting that this does not help against an attacker who already has such access and can be difficult to enforce on multi-user or jump hosts. Additional containment for environments where a foothold is a realistic concern includes restricting local logon rights and privileged account caching so an escalation primitive yields less value, since this vulnerability is a post-compromise step and not remotely reachable. Note that patch availability is confirmed but no public exploit identified at time of analysis, so deployment can follow a normal risk-based patch cycle rather than an emergency change process, though hosts granting local access to untrusted users should be prioritized.
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 root cause is CWE-416 (use-after-free) inside the Windows Search Component, the indexing and query subsystem that includes the Windows Search service (WSearch) and the associated search/indexer libraries shipped with client and server Windows. A use-after-free means the component retains a pointer to a heap object after that object has been freed; if an attacker can influence the timing, size, or content of the subsequent allocation, the freed slot can be reoccupied with attacker-controlled data and the stale reference is then dereferenced. In a search component this class of bug typically surfaces in parsing or indexing paths where buffers or objects are released during error handling and later touched again, producing memory corruption that can be steered into control-flow or data corruption and thus into privileged code execution in the context of the service. The associated tags (Use After Free, Memory Corruption, Denial Of Service) are consistent with this: the same defect can crash the component for a denial-of-service effect, or be shaped into reliable escalation. The assessed vector is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, so reachability is strictly local and requires an already-authenticated low-privileged principal; there is no remote, network, or unauthenticated path described, and the component is enabled by default on client Windows and present across the listed Server SKUs, which broadens the number of hosts where the primitive is available after a foothold. The EUVD affected-version data identifies the exposure by build number rather than CPE, with each Windows release fixing at its own build (for example 10.0.26100.9711 for Windows 11 24H2 and 25H2 10.0.26200.9711, 10.0.19044.7807 for Windows 10 21H2/22H2, and 10.0.26100.33650 for Windows Server 2025).
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 use-after-free EoP requiring an existing low-privileged account (AV:L, PR:L), no user interaction, low complexity, yielding full SYSTEM-level C/I/A impact without scope change.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Use after free in Microsoft Windows Search Component allows an authorized attacker to elevate privileges locally.
Executive ViewAI
Microsoft Windows Search Component contains a local privilege escalation vulnerability (CVE-2026-96324) that allows an authenticated attacker with existing low-privileged code execution to elevate to higher integrity levels, potentially compromising the confidentiality, integrity, and availability of affected Windows hosts. Although no public exploit has been identified at the time of analysis, this post-compromise escalation primitive poses a significant risk to organizations because it can enable attackers to deepen their foothold, access sensitive data, or move laterally after an initial breach. Leadership should prioritize patching to mitigate this high-severity threat across all Windows systems.
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
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.
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-100227
GHSA-mp9m-c49m-35g3
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB