Skip to main content

Windows Storage EUVDEUVD-2026-99841

| CVE-2026-69856 HIGH
Race Condition (CWE-362)
2026-10-13 secure@microsoft.com GHSA-wrqv-jwhc-px3f
7.0
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 account
  2. Delivery
    Invoke vulnerable Windows Storage path
  3. Exploit
    Win use-after-free race window
  4. Execution
    Corrupt freed kernel object
  5. Impact
    Execute code as SYSTEM

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Concurrency control, locking
MITRE ATT&CK

1 technique across 1 tactic: 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 have a local, authenticated foothold on the Windows host with at least low/standard user privileges (CVSS PR:L, AV:L) - there is no network-facing vector and no user interaction is needed (UI:N). The attacker must also win a race condition (CWE-362) to trigger the use-after-free, reflected in AC:H; this timing dependency makes exploitation non-deterministic and, per CISA SSVC, not automatable, so success typically requires repeated attempts. Limiting factors for defenders: mandatory prior authentication, local-only access, and the inherent unreliability of the race mean this is realistically a post-compromise privilege-escalation step rather than an initial-access or remotely exploitable flaw. Affected systems are those running Windows builds below the patched versions listed in the EUVD data across Windows 10, 11, and Server 2019/2022/2025.

Impact

This is a genuine but second-tier priority. 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) describes a local, already-authenticated attacker who must win a race condition (CWE-362 use-after-free) to achieve full confidentiality, integrity and availability impact on the host. The signals are internally consistent and point AWAY from mass exploitation: CISA SSVC records Exploitation=none and Automatable=no (the race window makes it non-scriptable at scale), which aligns with AC:H in the CVSS vector. Technical Impact=total matches the C:H/I:H/A:H triad, confirming that a successful exploit yields complete SYSTEM-level compromise. No EPSS score was provided, and there is no CISA KEV listing and no public POC in the supplied data, so there is no evidence of in-the-wild use. The one conflict worth flagging: the input Tags include 'Denial Of Service', but the description and CVSS clearly characterize this as an elevation-of-privilege use-after-free, not a DoS primitive (A:H here reflects the EoP's total impact, not a dedicated availability attack) - treat the DoS tag with skepticism. Net: a credible local privilege-escalation bug useful as a post-compromise step, patch-worthy on normal Patch-Tuesday cadence, but not an emergency given the local vector, prior-authentication requirement, race-condition complexity, and absence of exploitation evidence.

Exploit ScenarioDerived

A local, low-privileged authenticated user (or malware already running in a limited user context) runs a program that rapidly and repeatedly triggers the vulnerable Windows Storage code path, racing to reuse a freed object before it is reallocated. Winning the race corrupts kernel/driver memory and lets the attacker execute code or manipulate state at SYSTEM level, elevating from a standard user to full host control. No public exploit code is identified at time of analysis, and the race-condition requirement (CVSS AC:H) means the attack is unreliable and must often be retried.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% 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 the Windows Storage component of Windows 10, Windows 11, and Windows Server 2019/2022/2025 allows an authenticated attacker with standard user rights to raise their privileges to SYSTEM level on the affected host. Exploitation requires an existing local foothold and winning a timing race in the storage stack (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), so this is realistically a post-compromise escalation step rather than an initial-access or network-reachable flaw; there is no public exploit identified at time of analysis and CISA's SSVC assessment records exploitation as none and automatable as no. Microsoft rates the issue 7.0 High and vendor patches are available for all affected branches.

RemediationAI

Patch available per vendor advisory: apply Microsoft's security update for CVE-2026-69856 (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69856), which moves each branch to at least the fixed builds 10.0.17763.9376 for Windows 10 1809/Server 2019, 10.0.19044.7807 for Windows 10 21H2/22H2, 10.0.22631.7652 for Windows 11 23H2, 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.20348.5761 for Windows Server 2022, and 10.0.26100.33650 for Windows Server 2025 (including Server Core installations); verify the installed build with winver or Get-ComputerInfo and prioritize internet-facing and multi-user hosts first. Because this requires a local authenticated foothold and an unreliable race, compensating controls are secondary to patching: reduce the pool of low-privilege local accounts and restrict interactive/RDP logon on sensitive servers (trade-off: reduced administrative convenience, and it does not stop an attacker who already has a valid session), enforce least privilege and remove unnecessary local group membership so fewer principals can issue storage operations, and monitor for repeated anomalous storage IOCTL activity, unexpected bugchecks, or processes abruptly transitioning to SYSTEM integrity as attack signatures (trade-off: crash telemetry is noisy and can be triggered by legitimate driver faults). Ensuring EDR/AV kernel-level protections are active can also disrupt the memory-corruption primitive, but no configuration-only mitigation fully removes the underlying race window, so the vendor update remains the only complete fix.

Affected VersionsENISA

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 25H2 10.0.26200.0 <10.0.26200.9711
Windows Server 2019 10.0.17763.0 <10.0.17763.9376
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9376
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 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33650
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
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 22H2 10.0.19045.0 <10.0.19044.7807
Windows Server 2022 10.0.20348.0 <10.0.20348.5761

Affected Packages

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_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 13 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 flaw sits in the Windows Storage subsystem, the kernel-mode stack that handles disk, storage-space, and storage-driver operations, and is classified under CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization, i.e. a race condition) that results in a use-after-free of a storage-related object. A local caller able to issue storage operations can force an object to be freed while a concurrent path still holds a reference to it, producing a kernel memory-corruption condition; the CWE tags alongside the advisory (Race Condition, Denial Of Service) are consistent with this, since the same window can crash the host or be steered toward memory corruption. Because the corrupted structures are kernel-mode, successful exploitation yields code execution in the kernel context and full SYSTEM integrity (C:H/I:H/A:H), but the timing dependency (AC:H) makes success non-deterministic and, per SSVC, not automatable, so a working attack usually requires repeated attempts and prior authenticated local access (AV:L/PR:L with UI:N).

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.0 HIGH
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.0 HIGH

Local authenticated user (AV:L, PR:L) exploits a race-condition use-after-free (AC:H) needing no interaction (UI:N), yielding total SYSTEM compromise (C/I/A:H).

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:P/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
High
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:19 cve.org
HIGH 7.0

DescriptionCVE.org

Use after free in Windows Storage allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

A high-severity local privilege escalation vulnerability in the Windows Storage component affects Windows 10, Windows 11, and Windows Server 2019/2022/2025, allowing an attacker who already holds a standard user account on a host to elevate to SYSTEM-level control of that machine. The flaw is not remotely reachable and requires both an existing local foothold and a narrow timing condition in the storage stack, so it is best understood as a post-compromise escalation step that could deepen the impact of an initial intrusion rather than a new way in. Leadership should care because it raises the ceiling on any credential compromise or malware foothold already present on managed endpoints and servers, and vendor remediation across all affected branches is available now.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 90% exploitable
Prevalence
Ubiquitous
Core storage component present in all supported Windows client and server editions
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.2%
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
Medium
Technical Impact
Total

Priority Score

35
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +35
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Race conditions occur when multiple concurrent requests exploit the brief time gap between checking a condition and acting upon it (TOCTOU - Time of Check, Time of Use).

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

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