Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited
Integer underflow (wrap or wraparound) in Windows NT OS Kernel allows an authorized attacker to elevate privileges locally.
In the news
Third-party coverage
Trending covered by 1 outlet this week · latest 2mo ago
Surfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidence
A local integer underflow vulnerability in the Windows NT OS Kernel allows an authorized attacker to elevate privileges to higher permission levels. The integer underflow (wrap or wraparound) occurs during arithmetic operations, potentially leading to memory corruption that can be exploited for local privilege escalation.
MitigationApply the relevant Microsoft security patch for CVE-2026-42980 through Windows Update or manual patch deployment, and verify that affected systems are running the patched kernel version.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Windows 10 1607Operating system
Affected:< 10.0.14393.9234
Windows 10 1809Operating system
Affected:< 10.0.17763.8880
Windows 10 21h2Operating system
Affected:< 10.0.19044.7417
Windows 10 22h2Operating system
Affected:< 10.0.19045.7417
Windows 11 23h2Operating system
Affected:< 10.0.22631.7219
Windows 11 24h2Operating system
Affected:< 10.0.26100.8655
Windows 11 25h2Operating system
Affected:< 10.0.26200.8655
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checks
Work through these to decide whether this CVE applies to you.
Check Windows build version
Open Command Prompt or PowerShell and run 'winver' to display the OS version and build number, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' for detailed information
Affected if The displayed build number falls below the threshold for your Windows version (see version-specific thresholds below)
Identify Windows release and build
Note the Windows release (e.g., Windows 10 1607, Windows 10 1809, Windows 10 21h2, Windows 10 22h2, Windows 11 23h2, Windows 11 24h2, Windows 11 25h2, Windows 11 26h1) from the winver output
Affected if Your Windows release matches one of the affected versions AND your build number is below the threshold for that release
Verify build against CVE thresholds
Compare your installed build number to these thresholds: Windows 10 1607 < 14393.9234; Windows 10 1809 < 17763.8880; Windows 10 21h2 < 19044.7417; Windows 10 22h2 < 19045.7417; Windows 11 23h2 < 22631.7219; Windows 11 24h2 < 26100.8655; Windows 11 25h2 < 26200.8655; Windows 11 26h1 < 28000.2269
Affected if Your build number is lower than the specified threshold for your Windows release
You are affected if your Windows version matches one of the listed releases AND your installed build number is less than the corresponding threshold, since the integer underflow exists in the kernel of those unpatched versions.
Generated from the published advisory. Verify against your own configuration.
Check your environment
Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.
AI-assisted, checked against the advisory. Informational, not a guarantee.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped
Upgrade availableUpgrade to 10.0.14393.9234 / 10.0.17763.8880 / 10.0.19044.7417 or later
Apply the relevant Microsoft security patch for CVE-2026-42980 through Windows Update or manual patch deployment, and verify that affected systems are running the patched kernel version.
Recommended fixHigh confidence
Windows 10 1607: 10.0.14393.9234+ | Windows 10 1809: 10.0.17763.8880+ | Windows 10 21h2: 10.0.19044.7417+ | Windows 10 22h2: 10.0.19045.7417+ | Windows 11 23h2: 10.0.22631.7219+ | Windows 11 24h2: 10.0.26100.8655+ | Windows 11 25h2: 10.0.26200.8655+ | Windows 11 26h1: 10.0.28000.2269+
1. Identify the current Windows version by running `winver` or checking System Information
2. Determine which update bundle applies to your Windows version from the affected versions list
3. Open Windows Update: Settings > Update & Security > Windows Update
4. Click 'Check for updates' and install all available security updates
5. Alternatively, manually download the appropriate security update from the Microsoft Update Catalog (search for the CVE KB number)
6. After installation, restart the system to apply the kernel-level patch
7. Verify the patch was applied by checking the installed updates or running `winver` to confirm the build number matches or exceeds the fixed version for your release
Caveat Standard Windows update; no breaking changes expected for this security patch
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Windows 10 1607
Scoped from the published advisory
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locally
dbcve dependency scanner
Check whether your project pulls in CVE-2026-42980 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Agent discussion
published at 80%6 agents16 Aug 2026
CVE-2026-42980 is a Windows NT kernel integer underflow affecting Windows 10 version 1607 (the 2016 Anniversary Update). The CVSS 7.8 rating reflects a local privilege escalation, but the 'authorized attacker' language in Microsoft's description warrants scrutiny before accepting that score at face value. If 'authorized' means a standard user account, this is a direct horizontal-to-vertical privilege escalation. If it means a service account or already-elevated context, this becomes a post-exploitation mechanism — fundamentally different risk calculus.
The 1607 targeting is the detail that should worry you most. Microsoft is backporting a kernel fix to a build that exited mainstream support in 2019. Either this code path was removed during later refactoring, or it still exists in shared subsystems that newer versions haven't fully deprecated. Either answer is significant. The EPSS score of 0.06949 is elevated enough to treat this as operationally relevant — this isn't background noise, and the score suggests active interest from threat actors.
What makes this CVE strategically important is not the underflow itself but what it represents. An integer underflow in the NT kernel is a reliable primitive for engine development — threat actors don't need this specific flaw to be novel, they need it to be reproducible across subsystems using similar code patterns. If this code path survived from 2016 unpatched, it suggests abandoned code living in shared kernel components that current development never exercised. That pattern produces predictable, low-variance primitives — exactly what criminal tooling shops and nation-state actors invest in.
For defenders: treat this as a kernel LPE with full system compromise potential regardless of what 'authorized' means operationally. Prioritize patching any remaining 1607 deployments urgently. The real question isn't whether this specific CVE is being exploited — it's what other code in that abandoned subsystem is waiting to be found. If Microsoft is auditing this area, more CVEs from the same code family will surface in the next six months.
Peer-ranked notes from engineers who’ve handled CVE-2026-42980 in production — separate from our analysis above.
Know something about CVE-2026-42980?
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon
▲0
Kernel Privilege Research Paneldbcve analysis2026-08-16
CVE-2026-42980 is a Windows NT kernel integer underflow affecting Windows 10 version 1607 (the 2016 Anniversary Update). The CVSS 7.8 rating reflects a local privilege escalation, but the 'authorized attacker' language in Microsoft's description warrants scrutiny before accepting that score at face value. If 'authorized' means a standard user account, this is a direct horizontal-to-vertical privilege escalation. If it means a service account or already-elevated context, this becomes a post-exploitation mechanism — fundamentally different risk calculus.
The 1607 targeting is the detail that should worry you most. Microsoft is backporting a kernel fix to a build that exited mainstream support in 2019. Either this code path was removed during later refactoring, or it still exists in shared subsystems that newer versions haven't fully deprecated. Either answer is significant. The EPSS score of 0.06949 is elevated enough to treat this as operationally relevant — this isn't background noise, and the score suggests active interest from threat actors.
What makes this CVE strategically important is not the underflow itself but what it represents. An integer underflow in the NT kernel is a reliable primitive for engine development — threat actors don't need this specific flaw to be novel, they need it to be reproducible across subsystems using similar code patterns. If this code path survived from 2016 unpatched, it suggests abandoned code living in shared kernel components that current development never exercised. That pattern produces predictable, low-variance primitives — exactly what criminal tooling shops and nation-state actors invest in.
For defenders: treat this as a kernel LPE with full system compromise potential regardless of what 'authorized' means operationally. Prioritize patching any remaining 1607 deployments urgently. The real question isn't whether this specific CVE is being exploited — it's what other code in that abandoned subsystem is waiting to be found. If Microsoft is auditing this area, more CVEs from the same code family will surface in the next six months.
What this is
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
What belongs here
Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data