Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local code execution
-
DeliveryInvoke vulnerable Win32 kernel operation
-
ExploitWin TOCTOU race window
-
ExecutionRead privileged kernel memory
-
ImpactLeak data to aid further escalation
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture TOCTOU prevention
|
| Exploitation Conditions | Exploitation requires the attacker to already possess authenticated low-privileged local code execution on the target Windows system (AV:L, PR:L) - this is not remotely reachable and requires no victim interaction (UI:N). The core limiting factor is the race condition itself: as a TOCTOU flaw (CWE-367) the attacker must reliably win a narrow timing window between the kernel's check and use of a resource, which the AC:H rating and SSVC 'Automatable: no' confirm is difficult and non-deterministic, likely needing many attempts. Impact is confined to information disclosure (C:H) with no integrity or availability effect, so the realistic payoff is leaked kernel data rather than direct compromise. The specific vulnerable Win32 kernel code path is not named in the available data, so no particular feature or configuration setting can be cited as a prerequisite; it applies to default configurations of the listed in-support Windows versions below the patched build numbers. |
| Impact | This is a genuinely low-priority issue despite being a kernel vulnerability. The CVSS 3.1 score of 4.7 (Medium) is driven by AV:L (local access required), AC:H (high complexity - winning the TOCTOU race window is non-deterministic), PR:L (the attacker must already have a low-privileged authenticated foothold), and an impact limited strictly to confidentiality (C:H/I:N/A:N) with no scope change (S:U). All signals converge toward low real-world risk rather than conflicting: CISA's SSVC framework rates Exploitation as 'none', Automatable as 'no' (consistent with the race condition that makes AC:H appropriate), and Technical Impact as only 'partial'. There is no CISA KEV listing and no public POC in the provided data, so there is no public exploit identified at time of analysis. No EPSS score was supplied, so quantitative exploitation probability cannot be stated. The one consistency check worth noting: the description says 'disclose information locally' and the vector's AV:L agrees - there is no network/local contradiction here. Net assessment: a defense-in-depth kernel info-disclosure bug most valuable as one link in a larger local exploit chain (e.g., defeating KASLR), not a standalone priority. Patch during normal cycles. |
| Exploit ScenarioDerived | An attacker who already has the ability to run low-privileged code on a Windows host (e.g., via a standard user account or a compromised low-integrity process) repeatedly triggers the vulnerable Win32 kernel operation to win a narrow time-of-check/time-of-use race window. On a successful race they read kernel memory contents that should be inaccessible, potentially leaking addresses or data useful for a subsequent privilege-escalation chain. The AC:H rating reflects that success is probabilistic and may require many attempts; no public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Information disclosure in the Windows Win32 Kernel Subsystem stems from a time-of-check time-of-use (TOCTOU) race condition (CWE-367) that lets a local attacker with existing low-privileged code execution leak kernel memory contents. The issue rates only CVSS 4.7 (AV:L/AC:H/PR:L/UI:N, C:H/I:N/A:N) because seizing the narrow check-to-use window is difficult and non-deterministic; CISA's SSVC assessment scores Exploitation as 'none' and Automatable as 'no', and no public exploit code has been identified at time of analysis. Every in-support Windows 10, Windows 11 (21H2 through 26H2) and Windows Server 2012 through 2025 build below its respective patched build number is affected, and Microsoft has published fixes via its update guide.
RemediationAI
Vendor-released patch: Microsoft has shipped fixes for this CVE in its monthly security updates, so apply the applicable build from the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-96853 - for example, Windows 10 22H2/21H2 to 10.0.19044.7807, Windows 10 1809 and Server 2019 to 10.0.17763.9376, Windows 10 1607 and Server 2016 to 10.0.14393.9612, Windows 11 23H2 to 10.0.22631.7652, Windows 11 24H2/25H2/26H2 to 10.0.26100.9711, 10.0.26200.9711 and 10.0.26300.9711 respectively, Windows 11 26H1 to 10.0.28000.3231, Server 2012 to 6.2.9200.26434, Server 2012 R2 to 6.3.9600.23470, Server 2022 to 10.0.20348.5761, and Server 2025 to 10.0.26100.33650. No configuration switch or feature can be disabled to remove the vulnerable Win32 kernel path, so compensating controls must target the prerequisite foothold: enforce least privilege, remove unnecessary local accounts, and use WDAC or AppLocker application allowlisting to make it harder for an attacker to first obtain the low-privileged local code execution the race requires, accepting that allowlisting can break line-of-business applications and needs careful staging. Because exploitation is local-only and difficult (AC:H, SSVC Exploitation 'none', Automatable 'no'), priority should follow normal patch cycles rather than emergency action, with elevated urgency only for multi-tenant or shared-workstation environments where untrusted users already run code; there is no indication of active exploitation to justify a different rollout cadence.
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-367, a time-of-check time-of-use race in a Win32 kernel code path where the check on a resource and its subsequent use are not atomic. Because the check and use are separated in time, a local thread that already holds low-privileged credentials on the machine can repeatedly interleave operations to win the window and cause the kernel to operate on data it should not return, yielding kernel memory disclosure. The CVSS vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N confirms the flaw is local-only (AV:L), requires low privileges (PR:L), needs no user interaction (UI:N), has high complexity (AC:H) due to the race, stays within the same security scope (S:U), and produces high confidentiality impact (C:H) with no integrity or availability effect. The advisory names no specific Win32 feature, syscall, or configuration toggle, so the exposure applies to default installations of the affected Windows builds; exploitation cannot be triggered remotely and does not result from anything the victim does or opens.
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:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Local-only TOCTOU race requires an authenticated low-priv foothold (AV:L, PR:L) and winning a timing window (AC:H); impact is confidentiality-only kernel info disclosure (C:H, I:N, A:N).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Time-of-check time-of-use (toctou) race condition in Windows Win32 Kernel Subsystem allows an authorized attacker to disclose information locally.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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-100236
GHSA-j2r6-f5fm-fw5v
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB