Skip to main content

Windows Win32 Kernel EUVDEUVD-2026-99878

| CVE-2026-70236 HIGH
Use After Free (CWE-416)
2026-10-13 secure@microsoft.com GHSA-9vwg-q9mg-mpp3
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 foothold
  2. Delivery
    Launch crafted process invoking Win32 kernel call
  3. Exploit
    Trigger use-after-free race in kernel object
  4. Execution
    Reclaim freed memory to corrupt kernel structures
  5. Impact
    Elevate to SYSTEM / full host compromise

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

Requires the attacker to already possess local, authenticated low-privilege access to the target Windows system (PR:L) and the ability to execute code that invokes the vulnerable Win32 kernel subsystem path. Exploitation is further limited by high attack complexity (AC:H): the use-after-free almost certainly depends on winning a race condition or precise memory-reclamation timing, making reliable exploitation difficult and non-deterministic. No user interaction is needed (UI:N) and no special product configuration is called out - the flaw is in the core kernel subsystem present in default installations of all affected Windows 10/11 and Windows Server builds - but the local-only vector (AV:L) means there is no remote or network-based exploitation path.

Impact

This is a genuine but not top-priority issue. The CVSS 3.1 vector (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, score 7.0 HIGH) describes a local-only privilege-escalation flaw that requires the attacker to already have low-level (authenticated) access and to win a high-complexity condition - consistent with a kernel use-after-free (CWE-416) that typically depends on a race or specific timing window. The signals are internally consistent and largely point AWAY from urgent mass exploitation: CISA SSVC reports Exploitation=none, Automatable=no (fits AC:H and the local vector - this cannot be sprayed remotely), though Technical Impact=total matches the C:H/I:H/A:H kernel-level compromise. No EPSS score was provided, KEV status is not listed (treated as not present), and no POC was indicated - so there is no public exploit identified at time of analysis. The realistic role of this bug is as a local post-compromise escalation primitive (e.g., sandbox escape or SYSTEM elevation after initial foothold), not an initial-access or wormable threat. Note the 'Denial Of Service' tag conflicts somewhat with the description, which explicitly states privilege elevation; UAF bugs can yield both, but the authoritative impact per the description and CVSS is EoP - treat the DoS tag as secondary/informational.

Exploit ScenarioDerived

An attacker who has already gained low-privileged code execution on a Windows host (e.g., via phishing, a compromised service account, or a browser sandbox) runs a crafted program that triggers the use-after-free in the Win32 kernel subsystem, reclaiming the freed object to corrupt kernel memory and elevate to SYSTEM. Because AC:H, the exploit must reliably win a race/timing condition, so it is not trivially stable. No public exploit was identified at time of analysis.

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 14, 2026

Local privilege escalation in the Windows Win32 Kernel Subsystem lets an attacker who already holds authenticated, low-privileged access on a host trigger a use-after-free in kernel memory and gain elevated (SYSTEM-level) code execution. The assessed vector (AV:L/AC:H/PR:L/UI:N) shows exploitation is confined to the local machine and is gated by high attack complexity - the memory-reclamation or race timing makes reliable exploitation difficult and non-deterministic - with no user interaction and no remote or unauthenticated path. Microsoft has released vendor patches for every affected Windows 10/11 and Windows Server build, and no public exploit code or confirmed active exploitation has been identified at time of analysis (CISA KEV not listed; SSVC exploitation: none, automatable: no).

RemediationAI

Apply the Microsoft security update from the MSRC update guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70236), which carries the vendor patch for CVE-2026-70236 and the exact fixed builds listed above - for example Windows 11 24H2 to 10.0.26100.9711, Windows 11 25H2 to 10.0.26200.9711, Windows Server 2025 to 10.0.26100.33650, Windows Server 2022 to 10.0.20348.5761, Windows Server 2019/Windows 10 1809 to 10.0.17763.9376, Windows Server 2016/Windows 10 1607 to 10.0.14393.9612, Windows Server 2012 R2 to 6.3.9600.23470, and Windows Server 2012 to 6.2.9200.26434; prioritize multi-user hosts, RDP/VDI session hosts, and any system where untrusted users obtain interactive logons, since the vulnerability only matters once a low-privilege local foothold exists. There is no network-side mitigation because the vector is strictly local (AV:L) and the vulnerable code is a core kernel subsystem that cannot be disabled or firewalled off. Compensating controls are therefore limited to reducing the value of a low-privilege session and breaking post-exploitation chains: enforce least privilege and restrict interactive/RDP logon rights to trusted administrators, enable Credential Guard, LSA protection (RunAsPPL), HVCI/memory integrity, and WDAC/AppLocker or Defender attack-surface-reduction rules so that a compromised low-privileged account cannot easily convert kernel corruption into a durable SYSTEM-level breach; the trade-off is that these controls do not block the use-after-free itself and can break legacy applications, driver compatibility, or automation that relies on local interactive accounts. Because exploitation requires high-complexity timing and no public exploit code or active exploitation has been observed, patching can follow normal monthly-cadence risk prioritization rather than emergency change windows, but it should not be deferred indefinitely given the total technical impact score.

Affected VersionsENISA

Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26434
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7807
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9612
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33650
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.3231
Windows Server 2016 10.0.14393.0 <10.0.14393.9612
Windows 10 Version 22H2 10.0.19045.0 <10.0.19044.7807
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23470
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9612
Windows Server 2022 10.0.20348.0 <10.0.20348.5761
Windows Server 2012 6.2.9200.0 <6.2.9200.26434
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23470
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7652
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9376
Windows Server 2019 10.0.17763.0 <10.0.17763.9376
Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9376
Windows Server 2025 10.0.26100.0 <10.0.26100.33650

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 fix: 6.2.9200.26434
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_2012_server_core_installation fix: 6.2.9200.26434
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 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 flaw is a use-after-free (CWE-416) in the Windows Win32 kernel subsystem - the kernel-mode component (win32k/win32kbase and related drivers) that implements Windows graphics, window management, and a large part of the Win32 API surface inside the kernel. A use-after-free occurs when a kernel object is freed while a stale reference to it remains reachable; an attacker who can arrange for that freed pool allocation to be reclaimed with controlled data can substitute attacker-influenced contents for the object, corrupting kernel state and, in the worst case, obtaining arbitrary kernel read/write that is converted into privilege escalation. Consistent with the assessed vector (AV:L, AC:H, PR:L), the primitive almost certainly depends on winning a race or hitting a precise reclamation window rather than a deterministic call sequence, which is why the complexity is rated high despite the high confidentiality, integrity, and availability impact (S:U). The associated tags (denial of service, memory corruption) reflect that a failed or partial exploitation attempt will typically crash the box rather than succeed cleanly. Because the vulnerable code is in the core subsystem present in default installations of all affected Windows client and server builds, no special product configuration is required - only the ability to reach the affected kernel path from an already-established low-privilege session.

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-only kernel EoP requiring an existing low-priv account (PR:L) and a race to trigger the UAF (AC:H); successful exploit yields full kernel 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:H/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
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 Win32 Kernel Subsystem allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

Microsoft Windows 10, Windows 11, and Windows Server deployments are exposed to a local privilege-escalation vulnerability that could let an authenticated low-privilege user turn an existing foothold into SYSTEM-level control of the host. This raises the potential for unauthorized data access, persistence, and lateral movement on unpatched endpoints, making patch prioritization important for leadership even though no public exploit identified at time of analysis and exploitation requires local access with high complexity. Because a vendor patch is available per the Microsoft advisory, the organization can materially reduce risk through normal patch management.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 81% exploitable
Prevalence
Ubiquitous
Windows OS and Server across all supported versions; near-universal enterprise footprint
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation More 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

35
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +35
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.

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