Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconObtain low-privileged network credentials
-
DeliveryReach target over network
-
ExploitInduce privileged user or service interaction
-
InstallTrigger kernel UAF in network-reachable code path
-
C2Reclaim freed kernel memory with attacker-controlled data
-
ExecuteExecute arbitrary code at ring-0
-
ImpactFull OS 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 | Exploitation requires that the attacker holds at least a low-privileged authenticated account on or with network access to the target system (PR:L) - anonymous or unauthenticated network exploitation is not indicated by the CVSS vector. Additionally, user interaction is required (UI:R), meaning a second party such as a logged-in privileged user or an automated service must perform an operation that traverses the vulnerable kernel code path. The network attack vector (AV:N) applies to all listed Windows versions from Server 2012 through Windows 11 26H1 in their default configurations, provided the attacker meets both the authentication and user-interaction prerequisites. Exploitation is further constrained by high attack complexity (AC:H), consistent with the need to achieve specific heap state or race-condition timing to successfully reclaim the freed kernel object. Systems where low-privileged accounts have no network reachability to the vulnerable component reduce exposure. |
| Impact | The CVSS base score of 7.1 correctly captures meaningful exploitation constraints: AC:H demands race-condition or heap-grooming precision, PR:L requires a valid authenticated session, and UI:R necessitates a victim action - collectively making opportunistic mass exploitation more difficult than a straightforward network-unauthenticated bug. No EPSS data was provided and no CISA KEV listing exists, suggesting widespread active exploitation has not been observed. Nevertheless, the absolute attack surface is vast: even a mid-sized municipal IT team in tczew managing a mixed Windows Server 2019 and Windows 10 fleet spans dozens of affected build lines, meaning the aggregate exposure across all Windows deployments worldwide is extraordinary. The network attack vector combined with kernel-level C:H/I:H/A:H impact keeps this squarely in the priority-patching tier despite the elevated complexity, particularly for environments where lateral movement by authenticated internal or compromised accounts is a realistic threat. |
| Exploit ScenarioDerived | An authenticated attacker with a standard domain account (PR:L) initiates a network interaction that traverses a vulnerable Windows Kernel code path, then manipulates heap layout to reclaim freed kernel memory with attacker-controlled data - requiring the attacker to also induce a privileged user or service to perform a triggering action (UI:R). With the freed object pointer redirected, the attacker achieves kernel-mode code execution and elevates to SYSTEM or equivalent. No public exploit code has been identified at time of analysis, and the AC:H metric reflects the precision required to reliably trigger and win the race or heap condition. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 08, 2026
Privilege escalation via use-after-free in the Windows Kernel exposes an enormous swath of the Microsoft ecosystem - spanning Windows 10 1607 and Server 2012 through Windows 11 26H1 and Server 2025 - to network-reachable elevation of privilege by an authenticated attacker. The CVSS vector (AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H) indicates that exploitation is constrained by high complexity and a required victim interaction, but a successful attack yields full kernel-level confidentiality, integrity, and availability impact. Microsoft has released patches for all affected versions; no public exploit code or CISA KEV listing has been identified at time of analysis.
RemediationAI
Apply the Microsoft security update corresponding to each affected Windows version via Windows Update or WSUS; the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-68846 is the authoritative source. Vendor-confirmed patched builds are: Windows 11 24H2 and 25H2 to 10.0.26100.9445, Windows 11 26H1 to 10.0.28000.2954, Windows 11 23H2 to 10.0.22631.7582, Windows 10 21H2 and 22H2 to 10.0.19045.7725, Windows 10 1607 and Server 2016 to 10.0.14393.9512, Windows 10 1809 and Server 2019 to 10.0.17763.9245, Windows Server 2022 to 10.0.20348.5622, Windows Server 2025 to 10.0.26100.33438, Windows Server 2012 to 6.2.9200.26349, and Windows Server 2012 R2 to 6.3.9600.23397. Where immediate patching is not feasible, enforce strict network segmentation to limit which authenticated accounts can reach vulnerable kernel network paths, and apply the principle of least privilege to reduce the set of accounts that could serve as PR:L stepping stones; note that neither control eliminates the vulnerability and patch deployment remains the only confirmed fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 19 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-416 (Use After Free) describes a memory-safety defect in which a program accesses heap memory after it has been freed, enabling an attacker who controls the reclaimed region to redirect execution or corrupt kernel state. In the Windows NT kernel - ring-0 with no sandbox above it - exploitation of such a flaw immediately grants OS-level control. The AV:N metric indicates the vulnerable code path is reachable over the network, likely through a kernel-mode network stack component or a networked IPC mechanism. AC:H reflects the typical exploitation profile for kernel UAF: precise heap spray, race-condition timing, or both are required to reliably reclaim freed memory with attacker-controlled data. The affected build ranges span kernel version 6.2 (Windows Server 2012) through 10.0.28000 (Windows 11 26H1), indicating the vulnerable code has persisted across approximately a decade of Windows kernel releases without remediation.
Know when Windows 10 1607 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:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
Network vector accepted per description 'over a network'; AC:H reflects UAF heap-state or race-condition precision requirement; PR:L and UI:R per 'authorized attacker' and required interaction; full C/I/A from kernel-level compromise.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Use after free in Windows Kernel allows an authorized attacker to elevate privileges over a network.
Executive ViewAI
A privilege escalation vulnerability in the Windows Kernel affects nearly all Windows 10, Windows 11, and Windows Server instances deployed across enterprises (versions 2012 through 2025). Although exploitation requires an authenticated attacker with low privileges plus user interaction, successful attacks grant complete kernel-level system compromise. The breadth of affected systems and severity of impact if exploited make this a material risk to organizational security posture.
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.
More in Windows 10 1607
View allWindows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX
<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi
Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f
The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows
The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co
Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth
The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited
Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
EUVD-2026-73200
GHSA-v37x-22cx-h4pm
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB