Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local session
-
DeliveryTrigger use-after-free in Windows Update
-
ExploitGroom heap to control freed object
-
ExecutionHijack execution flow
-
ImpactElevate privileges to SYSTEM
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 the attacker to already hold a local, authenticated low-privileged account on the target Windows system (AV:L, PR:L) - there is no remote or network-facing attack surface and no user interaction is needed (UI:N). The decisive limiting factor is the high attack complexity (AC:H): as a use-after-free, the attacker must reliably win a timing/race window and control the contents of the freed allocation, which is non-deterministic and typically requires heap grooming, making exploitation unreliable in practice. The affected component is Windows Update, present by default across the listed client and server builds; no non-default feature toggle is indicated by the description, so the primary gate is the pre-existing local foothold plus the race condition, not a special configuration. |
| Impact | This is a genuine but moderate-priority local privilege escalation. The CVSS 3.1 vector (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.0 HIGH) tells a consistent story: the attacker must already have a local foothold with at least low (authenticated) privileges, and successful exploitation is gated behind high attack complexity (AC:H) - characteristic of use-after-free (CWE-416) bugs that require winning a race or grooming heap/timing state to control the freed object. Signals align rather than conflict: there is no CISA KEV listing and no public exploit referenced, so this is not confirmed active exploitation, and the AC:H rating argues against trivial or automatable mass exploitation. EPSS and SSVC decision data were not provided in the input, so probabilistic exploitation likelihood and the automatable/exploitation-status dimensions cannot be assessed here - do not treat the absence as 'low risk', merely as unmeasured. The impact if exploited is severe (full C/I/A compromise, consistent with SYSTEM-level elevation from a low-privileged account), which is why this still warrants prompt patching, but the local vector plus high complexity make it a post-compromise escalation tool rather than an initial-access or wormable threat. |
| Exploit ScenarioDerived | An attacker who has already gained a low-privileged authenticated session on a Windows host (e.g., via phishing, stolen credentials, or a separate RCE) triggers the use-after-free condition in the Windows Update component to corrupt memory and hijand execution flow. By winning the required race/timing window (reflected in AC:H), they elevate from their low-privileged context to SYSTEM. No public proof-of-concept exploit was identified in the provided data, so exploitation currently requires original research. |
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 Windows Update component of unpatched Windows 10, Windows 11, and Windows Server installations lets a user who already holds a low-privileged local account corrupt memory and elevate to a higher-integrity context. Exploitation is gated by two factors: the attacker must already have an authenticated local foothold (AV:L, PR:L, no user interaction required), and the use-after-free is rated high attack complexity (AC:H) because it requires reliably winning a timing/race window and controlling the contents of the freed allocation, which is non-deterministic and typically needs heap grooming. No public exploit code has been identified at time of analysis, the vulnerability is not a confirmed actively exploited (CISA KEV) item, and Microsoft has released fixes, making this a genuine but moderate-priority privilege-escalation issue rather than a remotely reachable or wormable threat.
RemediationAI
Apply the vendor-released Windows cumulative update referenced in the MSRC advisory (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-96323); the EUVD data indicates the fix is delivered by raising each affected branch to or above the threshold builds listed in the affected-products field (for example 10.0.26100.33650 for Windows Server 2025, 10.0.26100.9711 for Windows 11 24H2, and 10.0.19044.7807 for Windows 10 21H2/22H2), so verify the installed build after servicing rather than assuming a single KB applies to every branch. The most effective compensating control is to remove the prerequisite local foothold: enforce least privilege, restrict who can maintain an interactive session or run processes on servers, and audit local account usage, since the flaw cannot be reached over the network and requires an authenticated local user. As a tighter but more disruptive measure, administrators can stop and disable the Windows Update (wuauserv) service on high-value hosts; the trade-offs are that this halts all future servicing and vendor patch delivery (including the fix for this CVE) and may not fully close every code path that touches the servicing stack, so it should be treated as a short-term containment step only. Because the bug is a heap use-after-free with a race component, broader exploit-mitigation and monitoring layers - heap integrity protections, exploit protection policies, and detection of unexpected child processes or token changes spawned from servicing-related processes - are worthwhile supporting controls, but they reduce reliability or detection time rather than substituting for the patch.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 10 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This is a memory-safety defect classified as CWE-416 (Use After Free) inside Windows Update, the servicing stack that runs by default on modern Windows client and server builds. In a use-after-free, a pointer to a heap allocation is retained and dereferenced after that object has been freed, so the attacker can influence what is placed into the reallocated memory (a classic heap-grooming primitive) and thereby redirect control flow or corrupt adjacent structures from within a low-privileged process that interacts with the servicing component. Because the flaw lives in a component that typically operates at a higher integrity level, successful corruption translates directly into privilege elevation, which is consistent with the equal High Confidentiality, Integrity, and Availability sub-scores in the assessed vector (C:H/I:H/A:H, Scope Unchanged). The accompanying tags for memory corruption and denial of service reflect the same root cause: an uncontrolled free/reuse can crash the process as easily as it can be steered into code execution. The assessed vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N matches the advisory-intelligence vector, so both sources agree that this is a local, authenticated, race-dependent primitive with no network-facing attack surface and no special non-default feature toggle - the only prerequisite is a pre-existing local session.
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:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Local use-after-free EoP requiring an existing low-privileged account (PR:L) and a hard-to-win race condition (AC:H), yielding full SYSTEM compromise (C:H/I:H/A:H).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Use after free in Windows Update allows an authorized attacker to elevate privileges locally.
Executive ViewAI
A local privilege-escalation flaw in the Microsoft Windows Update component affects Windows 10, Windows 11, and Windows Server systems that have not yet applied current updates. It does not give an outsider a way in; it lets someone who already holds a low-privileged account on a machine - such as a contractor, shared-workstation user, or an attacker who has landed a basic foothold - attempt to gain higher-integrity rights, which could open the door to broader lateral movement and data access. Because successful exploitation requires an existing local account and a difficult-to-win timing condition, leadership should treat this as a patching-hygiene priority rather than an emergency, though unmanaged or shared endpoints carry the most exposure.
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-100224
GHSA-j482-5x26-226r
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB