Skip to main content
View

Attack ChainAIDerived

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

  1. Recon
    Obtain low-priv local execution
  2. Delivery
    Identify vulnerable kernel syscall path
  3. Exploit
    Trigger integer underflow with crafted input
  4. Install
    Corrupt kernel heap pool object
  5. C2
    Overwrite token or callback pointer
  6. Execute
    Elevate process to SYSTEM
  7. Impact
    Disable defenses and persist

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 the attacker to already possess authenticated local code execution as a low-privileged user on the target Windows system (CVSS PR:L, AV:L), meaning this is not directly exploitable from the network or by anonymous users. No user interaction is required once the attacker has local execution (UI:N), and no special non-default Windows configuration, optional feature, or specific hardware is identified in the description as a prerequisite - the vulnerable code path is in the core NT kernel and presumed reachable on default installations of affected Windows versions. Practical limits on exploitation are the local-access requirement and the need for the attacker to craft a working kernel heap-grooming primitive, which raises exploit-development complexity above trivial userland bugs but is well within the capability of mid-tier offensive actors.

Impact

The CVSS 7.8 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) accurately characterizes this as a local, low-complexity, low-privilege EoP with full CIA impact - a profile typical of kernel pool corruption flaws. No EPSS score, KEV listing, or SSVC decision data is provided in the input, so probabilistic exploitation likelihood cannot be quantitatively assessed. The bug is not remotely exploitable in isolation (AV:L), meaning real-world risk depends on the attacker already having code execution as a standard user - a condition routinely met after phishing, browser exploits, or commodity malware infection. Kernel EoP vulnerabilities of this exact class are historically high-value targets for ransomware affiliates and offensive tooling, so although no public exploit is identified at time of analysis, the latent risk over the patch lifecycle is meaningful and this should not be deprioritized merely because it is 'local-only'.

Exploit ScenarioDerived

An attacker first obtains low-privileged code execution on a Windows host through a phishing payload, malicious document, or stolen standard-user credentials. They then run a crafted user-mode program that issues syscalls or IOCTLs designed to trigger the integer underflow in the NT kernel, corrupting heap pool memory to overwrite a kernel object (commonly a token or callback pointer) and pivot to SYSTEM privileges. No public exploit is identified at time of analysis, but the bug class is well-understood and proof-of-concept development would be feasible for a skilled exploit writer.

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 attacker to elevate to SYSTEM by triggering an integer underflow condition. With a CVSS of 7.8 and no public exploit identified at time of analysis, this issue is primarily a post-compromise escalation vector commonly chained after initial access via phishing or commodity malware. Microsoft has released a patch through MSRC, and given Windows kernel EoP bugs are frequently weaponized by ransomware and APT actors historically, prompt patching is warranted despite the absence of confirmed in-the-wild exploitation.

RemediationAI

Apply the Microsoft-released security update referenced at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-42980 - patch available per vendor advisory, though the specific KB number and exact fixed kernel build are not enumerated in the input data and must be retrieved from MSRC for each affected Windows SKU. Prioritize patching multi-user systems, terminal servers, VDI hosts, and developer workstations where untrusted local code is most likely to execute. Until patching is complete, compensating controls include restricting local logon rights to trusted accounts via Group Policy (User Rights Assignment), enforcing application allowlisting through Windows Defender Application Control or AppLocker to prevent unsigned attacker binaries from running, and enabling Microsoft Defender for Endpoint with attack surface reduction rules to detect post-exploitation kernel-mode behavior - noting that AppLocker bypasses are well-known and these controls only raise the bar rather than eliminate the vector.

Affected VersionsENISA

Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.32995
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7219
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26132
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9234
Windows Server 2022 10.0.20348.0 <10.0.20348.5256
Windows Server 2019 10.0.17763.0 <10.0.17763.8880
Windows Server 2025 10.0.26100.0 <10.0.26100.32995
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.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 Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.8880
Windows Server 2012 6.2.9200.0 <6.2.9200.26132
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.8655
Windows Server 2016 10.0.14393.0 <10.0.14393.9234
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9234
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.2269
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23228
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.8880
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23228
Windows 11 version 26H1 1.0.0 <10.0.28000.2269

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
microsoft windows_11_version_26h1_extra_10_0_28000_2269 fix: Windows 11 Version 26H1 for x64-based Systems - extra 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 34 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 Windows NT OS Kernel - the core ring-0 component (ntoskrnl.exe) responsible for memory management, process scheduling, and system call handling. The root cause is CWE-122 (Heap-based Buffer Overflow), here triggered through an integer underflow/wraparound: an arithmetic operation on an unsigned value produces a value larger than expected, which is then used as a size or index for a heap allocation or copy, resulting in out-of-bounds writes within kernel pool memory. The 'Buffer Overflow, Heap Overflow' tags confirm the bug manifests as a heap corruption primitive in kernel space, which when exploited successfully grants attackers arbitrary kernel read/write and full SYSTEM privileges. Specific affected Windows builds are not enumerated in the available data and must be retrieved from MSRC.

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

Windows NT Kernel local privilege escalation (CVE-2026-42980) enables authenticated attackers to escalate to SYSTEM privileges, creating post-compromise risk across Windows infrastructure used by ransomware and advanced persistent threat actors. Organizations face elevated risk that initial access via phishing or commodity malware will be followed by privilege escalation and lateral movement to critical systems. Microsoft has released a patch; immediate deployment is critical to reduce the attack surface for ransomware groups and APT campaigns.

Business Impact: High
Compensating Controls

Apply vendor patch (MSRC release). Until fully deployed, implement network segmentation and EDR solutions to detect post-compromise privilege escalation attempts; restrict administrative account usage to essential systems only.

Threat Intelligence Overview

EPSS Score
0.1%
Top 71% 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 More 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

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.

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