Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Obtain low-privileged local access
  2. Delivery
    Invoke vulnerable kernel syscall/IOCTL
  3. Exploit
    Trigger integer underflow wraparound
  4. Install
    Corrupt kernel memory structures
  5. C2
    Overwrite process token to SYSTEM
  6. Execute
    Disable security tooling and persist
  7. Impact
    Lateral movement across domain

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer overflow checks
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

The attacker must already possess valid low-privilege credentials and the ability to execute code locally on the target Windows host (CVSS AV:L/PR:L); no user interaction by a separate victim is required (UI:N) and attack complexity is low (AC:L). Exploitation is limited to scenarios where the attacker can invoke the vulnerable kernel code path directly, which generally means logged-on interactive sessions, Remote Desktop sessions, or code execution achieved through a prior bug or malicious binary - purely remote network-only attackers cannot trigger this issue. No special non-default Windows configuration is called out in the description, so default installations of affected Windows builds running the NT OS Kernel are in scope.

Impact

Signals are consistent and point to a credible but not emergency-grade risk. The CVSS vector (AV:L/AC:L/PR:L/UI:N) confirms local attack vector with low complexity and only low privileges required - a realistic precondition on multi-user systems, terminal servers, or any host already touched by an initial-access payload. C:H/I:H/A:H reflects full kernel compromise. There is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV, so this is not yet an active-exploitation emergency. However, Windows kernel EoP bugs are a historically reliable target for commodity malware and ransomware operators once details land, and the Microsoft-internal report by secure@microsoft.com suggests responsible disclosure rather than third-party discovery in the wild. EPSS and SSVC values were not provided in the input, so probabilistic exploitation likelihood cannot be independently quantified.

Exploit ScenarioDerived

An attacker who has already obtained a low-privileged foothold on a Windows host - for example via a phishing payload, stolen standard-user credentials, or a compromised RDP session - runs a local tool that triggers the integer underflow in a kernel syscall or IOCTL handler. The wraparound corrupts kernel memory, allowing the attacker to overwrite a token or function pointer and elevate to SYSTEM, after which they disable EDR, dump LSASS, and pivot. No public exploit is identified at time of analysis, but kernel integer-bug exploitation is well-documented and proof-of-concept work historically appears within weeks of patch release.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 09, 2026

Local privilege escalation in the Windows NT OS Kernel allows an authenticated low-privileged user to elevate to higher privileges through an integer underflow condition. The flaw carries a CVSS 7.8 (High) rating with no public exploit identified at time of analysis, but Microsoft has issued a patch via MSRC. Defenders should treat this as a standard Patch-Tuesday-class kernel EoP that becomes a critical post-compromise pivot once initial access is achieved.

RemediationAI

Apply the Microsoft-released patch as published in the MSRC update guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-42916) by deploying the relevant cumulative update for each affected Windows client and server build through Windows Update, WSUS, or your standard patch management pipeline; exact KB identifiers are listed per-SKU in the MSRC entry. Because the vulnerability lives in the OS kernel itself, there is no feature toggle or configuration workaround - kernel patching is the only durable fix. As compensating controls until patching completes, restrict interactive and Remote Desktop logon rights on sensitive hosts to trusted administrators (reducing the pool of accounts that can satisfy the PR:L precondition, at the cost of reduced operational flexibility), enforce application allowlisting (e.g., WDAC or AppLocker) to limit unsigned binaries that would stage the exploit (cost: tuning effort and potential breakage of line-of-business apps), and prioritize endpoint detection coverage for anomalous token manipulation and kernel-mode driver loads. Refer to the vuldb tracking entry at https://vuldb.com/vuln/369616 for additional cross-referenced metadata.

Affected VersionsENISA

Windows 11 version 26H1 10.0.28000.0 <10.0.28000.2269
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26132
Windows Server 2019 10.0.17763.0 <10.0.17763.8880
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.8880
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9234
Windows Server 2012 6.2.9200.0 <6.2.9200.26132
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.8880
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9234
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23228
Windows Server 2025 10.0.26100.0 <10.0.26100.32995
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.32995
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.8655
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.8655
Windows 10 Version 22H2 10.0.19045.0 <10.0.19045.7417
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7417
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7219
Windows Server 2016 10.0.14393.0 <10.0.14393.9234
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23228
Windows Server 2022 10.0.20348.0 <10.0.20348.5256

Affected Packages

microsoft windows_10_version_1607_10_0_14393_9234 fix: Windows 10 Version 1607 for 32-bit Systems 10.0.14393.9234, Windows 10 Version 1607 for x64-based Systems 10.0.14393.9234
microsoft windows_10_version_1809_10_0_17763_8880 fix: Windows 10 Version 1809 for 32-bit Systems 10.0.17763.8880, Windows 10 Version 1809 for x64-based Systems 10.0.17763.8880
microsoft windows_10_version_21h2_10_0_19044_7417 fix: Windows 10 Version 21H2 for 32-bit Systems 10.0.19044.7417, Windows 10 Version 21H2 for ARM64-based Systems 10.0.19044.7417, Windows 10 Version 21H2 for x64-based Systems 10.0.19044.7417
microsoft windows_10_version_22h2_10_0_19045_7417 fix: Windows 10 Version 22H2 for 32-bit Systems 10.0.19045.7417, Windows 10 Version 22H2 for ARM64-based Systems 10.0.19045.7417, Windows 10 Version 22H2 for x64-based Systems 10.0.19045.7417
microsoft windows_11_version_23h2_10_0_22631_7219 fix: Windows 11 Version 23H2 for ARM64-based Systems 10.0.22631.7219, Windows 11 Version 23H2 for x64-based Systems 10.0.22631.7219
microsoft windows_11_version_24h2_10_0_26100_8655 fix: Windows 11 Version 24H2 for ARM64-based Systems 10.0.26100.8655, Windows 11 Version 24H2 for x64-based Systems 10.0.26100.8655
microsoft windows_11_version_25h2_10_0_26200_8655 fix: Windows 11 Version 25H2 for ARM64-based Systems 10.0.26200.8655, Windows 11 Version 25H2 for x64-based Systems 10.0.26200.8655
microsoft windows_11_version_26h1_10_0_28000_2269 fix: Windows 11 Version 26H1 for ARM64-based Systems 10.0.28000.2269, Windows 11 version 26H1 for x64-based Systems 10.0.28000.2269
microsoft windows_server_2012_6_2_9200_26132 fix: Windows Server 2012 6.2.9200.26132, Windows Server 2012 (Server Core installation) 6.2.9200.26132
microsoft windows_server_2012_r2_6_3_9600_23228 fix: Windows Server 2012 R2 6.3.9600.23228, Windows Server 2012 R2 (Server Core installation) 6.3.9600.23228
microsoft windows_server_2016_10_0_14393_9234 fix: Windows Server 2016 10.0.14393.9234, Windows Server 2016 (Server Core installation) 10.0.14393.9234
microsoft windows_server_2019_10_0_17763_8880 fix: Windows Server 2019 10.0.17763.8880, Windows Server 2019 (Server Core installation) 10.0.17763.8880
microsoft windows_server_2022_10_0_20348_5256 fix: Windows Server 2022 10.0.20348.5256, Windows Server 2022 (Server Core installation) 10.0.20348.5256
microsoft windows_server_2025_10_0_26100_32995 fix: Windows Server 2025 10.0.26100.32995, Windows Server 2025 (Server Core installation) 10.0.26100.32995
euvd windows_10_version_1607 fix: 10.0.14393.9234
euvd windows_10_version_1809 fix: 10.0.17763.8880
euvd windows_10_version_21h2 fix: 10.0.19044.7417
euvd windows_10_version_22h2 fix: 10.0.19045.7417
euvd windows_11_version_23h2 fix: 10.0.22631.7219
euvd windows_11_version_24h2 fix: 10.0.26100.8655
euvd windows_11_version_25h2 fix: 10.0.26200.8655
euvd windows_11_version_26h1 fix: 10.0.28000.2269
euvd windows_server_2012 fix: 6.2.9200.26132
euvd windows_server_2012_r2 fix: 6.3.9600.23228
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23228
euvd windows_server_2012_server_core_installation fix: 6.2.9200.26132
euvd windows_server_2016 fix: 10.0.14393.9234
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9234
euvd windows_server_2019 fix: 10.0.17763.8880
euvd windows_server_2019_server_core_installation fix: 10.0.17763.8880
euvd windows_server_2022 fix: 10.0.20348.5256
euvd windows_server_2025 fix: 10.0.26100.32995
euvd windows_server_2025_server_core_installation fix: 10.0.26100.32995

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 33 packages in microsoft, 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 core Windows NT OS Kernel, the privileged ring-0 component underpinning all supported Windows client and server SKUs. The root cause is CWE-190 (Integer Overflow or Wraparound) - specifically an integer underflow where an arithmetic operation produces a value below the representable minimum, wrapping around to a large unsigned value. In kernel code paths, such wraparound typically corrupts size calculations used in buffer allocation, length validation, or pointer arithmetic, enabling subsequent out-of-bounds writes or undersized buffer allocations that an attacker can leverage for memory corruption and ultimately arbitrary kernel-mode code execution.

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

Vendor (microsoft) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CIRCL (temporal) 6.8 MEDIUM

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Integer underflow (wrap or wraparound) in Windows NT OS Kernel allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

A kernel-level privilege escalation in Windows (CVE-2026-42916, CVSS 7.8) enables attackers who have gained initial system access to escalate to higher privilege levels, effectively converting any compromised user account into an administrator. This vulnerability significantly increases the impact of breaches across your Windows infrastructure, as it provides a guaranteed privilege escalation pathway post-compromise. Immediate patching of Microsoft's fix is critical to reduce your attack surface for lateral movement and persistent access.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.1%
Top 76% exploitable
Vendor Action
See Below
Required. The vulnerability documented by this CVE requires customer action to resolve.
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
6 sources
Confidence: High

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.1%
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
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

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

Attack Technique

Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Related Vulnerabilities in Windows NT OS Kernel Integer Underflow EoP

View all 2
CVE-2021-40444 HIGH POC
8.8 Sep 15

Windows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX

CVE-2021-34527 HIGH POC
8.8 Jul 02

<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi

CVE-2022-30190 HIGH POC
7.8 Jun 01

Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f

CVE-2017-0147 HIGH POC
7.5 Mar 17

The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows

CVE-2018-8174 HIGH POC
7.5 May 09

The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co

CVE-2021-1675 HIGH POC
7.8 Jun 08

Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth

CVE-2016-7255 HIGH POC
7.8 Nov 10

The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited

CVE-2023-36884 HIGH POC
7.5 Jul 11

Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo

CVE-2023-44487 HIGH POC
7.5 Oct 10

Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour

CVE-2024-30088 HIGH POC
7.0 Jun 11

Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR

CVE-2019-1458 HIGH POC
7.8 Dec 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

CVE-2018-8453 HIGH POC
7.8 Oct 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

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