dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-33837

HIGH · 7.8 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 10.0.14393.9140 / 10.0.17763.8755 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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
Heap-based buffer overflow in Windows TCP/IP allows an authorized attacker to elevate privileges locally.

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 · high confidence

A heap-based buffer overflow vulnerability exists in the Windows TCP/IP network stack. An authorized attacker with local access can exploit this memory corruption issue to elevate their privileges on the affected system, potentially gaining administrative or SYSTEM-level access.

MitigationApply the relevant Microsoft security patch for Windows TCP/IP when released. Prioritize patching systems with direct user access and implement least-privilege principles to limit local attacker access to sensitive resources.

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.9140
Windows 10 1809Operating system
Affected:< 10.0.17763.8755
Windows 10 21h2Operating system
Affected:< 10.0.19044.7291
Windows 10 22h2Operating system
Affected:< 10.0.19045.7291
Windows 11 23h2Operating system
Affected:< 10.0.22631.7079
Windows 11 24h2Operating system
Affected:< 10.0.26100.8390
Windows 11 25h2Operating system
Affected:< 10.0.26200.8390
Windows 11 26h1Operating system
Affected:< 10.0.28000.2113

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.

  1. Determine installed Windows version
    Run 'winver' from command prompt or check System Properties, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
    Affected if The displayed version/build number is lower than any of the affected version thresholds (10.0.14393.9140, 10.0.17763.8755, 10.0.19044.7291, 10.0.19045.7291, 10.0.22631.7079, 10.0.26100.8390, 10.0.26200.8390, 10.0.28000.2113)
  2. Obtain exact build number via registry
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' and 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v UBR' to get full build (CurrentBuild.UBR)
    Affected if The combined build number (CurrentBuild.UBR) is lower than the affected version for your Windows release
  3. Confirm TCP/IP networking is enabled
    Run 'netsh interface show interface' or check Network Adapter status in Control Panel; TCP/IP is enabled by default on any active network adapter
    Affected if TCP/IP is bound to any active network adapter (this is the default state for most Windows installations)

The system is affected if it runs any Windows 10 or 11 version with a build number lower than the threshold for that release, and TCP/IP networking is enabled (which is the default state).

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 available Upgrade to 10.0.14393.9140 / 10.0.17763.8755 / 10.0.19044.7291 or later
Fixed in 10.0.14393.914010.0.17763.875510.0.19044.7291
Interim mitigation

Apply the relevant Microsoft security patch for Windows TCP/IP when released. Prioritize patching systems with direct user access and implement least-privilege principles to limit local attacker access to sensitive resources.

Recommended fix High confidence

Windows 10 1607 build 10.0.14393.9140 or later | Windows 10 1809 build 10.0.17763.8755 or later | Windows 10 21h2 build 10.0.19044.7291 or later | Windows 10 22h2 build 10.0.19045.7291 or later | Windows 11 23h2 build 10.0.22631.7079 or later | Windows 11 24h2 build 10.0.26100.8390 or later | Window

  1. Check current Windows version by running `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"`
  2. Open Settings > Windows Update > Check for updates, or run `ms-settings:windowsupdate`
  3. Install all available security updates, specifically the Windows TCP/IP security update (referenced on MSRC)
  4. Restart the computer when prompted to complete the installation
  5. Verify the update was applied by checking the OS build version matches or exceeds: Windows 10 1607: 10.0.14393.9140 | Windows 10 1809: 10.0.17763.8755 | Windows 10 21h2: 10.0.19044.7291 | Windows 10 22h2: 10.0.19045.7291 | Windows 11 23h2: 10.0.22631.7079 | Windows 11 24h2: 10.0.26100.8390 | Windows 11 25h2: 10.0.26200.8390 | Windows 11 26h1: 10.0.28000.2113
Caveat Standard Windows cumulative update apply; no special breaking changes expected for this privilege escalation patch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33837 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33837 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

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