Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain physical access to target device
-
DeliveryDeliver crafted input to Win32 kernel subsystem
-
ExploitOverflow heap buffer in kernel memory
-
ExecutionCorrupt kernel structures to execute attacker-controlled code
-
ImpactElevate to SYSTEM privileges
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires physical access to the target device (CVSS AV:P) - the attacker must be able to interact directly with the machine's hardware or local console rather than over any network. Within that constraint, no authentication is required (PR:N) and no user interaction is needed (UI:N), and the attack complexity is low (AC:L), so once physical access is obtained, exploitation against affected Windows builds is straightforward. The decisive limiting factor is the physical-access prerequisite, which confines realistic risk to insiders, shared/kiosk endpoints, or lost/stolen devices rather than remote attackers. Affected systems are Windows 10 (1809/21H2/22H2), Windows 11 (23H2/24H2/25H2/26H1/26H2), and Windows Server 2019/2022/2025 below the patched build numbers listed in EUVD-2026-100028. |
| Impact | This is a genuinely moderate-priority issue rather than a top-tier emergency, and the signals are consistent rather than conflicting. The CVSS 3.1 vector (AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 6.8) is capped at MEDIUM severity specifically because the attack vector is physical (AV:P) - an attacker must have hands-on access to the device, which sharply limits scalability despite the total CIA impact of a successful privilege escalation. CISA's SSVC decision data reinforces this: Exploitation is 'none' (no observed exploitation), Automatable is 'no' (physical access cannot be scripted or wormed at scale), and Technical Impact is 'total' (consistent with the C:H/I:H/A:H kernel-level compromise). The vulnerability is NOT in CISA KEV and no POC is referenced in the provided data, so exploitation status is 'no public exploit identified at time of analysis.' There is no EPSS score in the input to weigh, so widespread-exploitation probability cannot be quantified here. The honest bottom line: a high technical impact (kernel heap overflow → full elevation of privilege) gated behind a physical-access precondition that makes it a targeted/insider or lost-device concern rather than a remote-mass-exploitation threat. Patch promptly on a normal cadence; it does not warrant emergency out-of-band response absent a change in exploitation status. |
| Exploit ScenarioDerived | An attacker with physical access to an unlocked or accessible Windows machine (e.g., an insider, or someone handling a lost/stolen/kiosk/shared device) triggers a crafted input to the Win32 kernel subsystem that overflows a heap buffer (CWE-122), corrupting kernel memory to escalate from an unauthorized context to SYSTEM-level privileges. No public exploit code is identified in the provided data, and the physical attack vector (AV:P) means the attack cannot be performed remotely or automated at scale. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Privilege escalation in the Windows Win32 Kernel Subsystem stems from a heap-based buffer overflow (CWE-122) that an attacker with physical access to a target machine can trigger to gain SYSTEM-level privileges; once physical contact is achieved, no authentication or user interaction is required. Microsoft has released vendor patches, and no public exploit code or active exploitation has been identified at time of analysis (SSVC exploitation: none, automatable: no). Because the attack vector is physical (CVSS AV:P) with a 6.8 score, realistic risk is limited to insiders, shared or kiosk endpoints, and lost or stolen devices rather than remote attackers.
RemediationAI
Apply Microsoft's vendor-released patches; the fixed builds per EUVD-2026-100028 are the version thresholds listed above (e.g., 10.0.17763.9376 for Windows 10 1809/Server 2019, 10.0.19044.7807 for Windows 10 21H2/22H2, 10.0.20348.5761 for Server 2022, 10.0.22631.7652 for Windows 11 23H2, and the 10.0.26100/26200/26300/28000 thresholds for Windows 11 24H2/25H2/26H2/26H1 and Server 2025). Install via Windows Update or the Microsoft Update Catalog, referencing https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83895. Because the vector is physical, prioritize patching kiosks, shared workstations, and portable devices, and as a compensating control restrict physical access to trusted personnel and consoles, enable BitLocker or device encryption, and use standard-user accounts (not local admin) on endpoint devices; note that physical-access controls add operational friction and are not a substitute for patching, and no public exploit exists so urgency is moderate rather than emergency.
Affected VersionsENISA
Affected Packages
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 vulnerability resides in the Windows Win32 kernel subsystem (win32k.sys), the kernel-mode component that implements the Win32 API and window manager/GDI functionality. CWE-122 (heap-based buffer overflow) means a heap-allocated buffer is written past its bounds during parsing or processing, potentially corrupting adjacent kernel heap structures; successful exploitation in kernel mode yields elevation of privilege to SYSTEM. The CVSS vector AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H confirms that the attacker must be physically present at the device, but that once there, no credentials or user interaction are needed and attack complexity is low, with high confidentiality, integrity, and availability impact. Affected CPE-identified products include Windows 10 1809/21H2/22H2, Windows 11 23H2/24H2/25H2/26H1/26H2, and Windows Server 2019/2022/2025 (including Server Core installations) below the fixed builds.
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
AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Physical access required so AV:P; low complexity and no auth or interaction per the kernel heap overflow description; full kernel compromise yields C/I/A:H with unchanged scope.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Heap-based buffer overflow in Windows Win32 Kernel Subsystem allows an unauthorized attacker to elevate privileges with a physical attack.
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
EUVD-2026-100028
GHSA-mc7v-cvhg-m66w
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB