dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50377

HIGH · 7.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.14393.9339 / 10.0.17763.9020 or later.
See remediation →
80/100
Remediation priority · High
Zero-click 5 weeks old

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
Out-of-bounds read in Windows Kernel allows an authorized attacker to elevate privileges locally.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1mo 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

Windows Kernel vulnerability involving an out-of-bounds read that enables local privilege escalation. The flaw allows an authorized (local) attacker to read memory beyond allocated boundaries, potentially achieving elevated (system/root-level) privileges on the affected Windows system.

MitigationApply vendor-supplied Windows security patches promptly. As this is a kernel-level vulnerability requiring local access, prioritize patch deployment to workstations and servers with direct user access, and follow least-privilege principles to limit exposure.

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.9339
Windows 10 1809Operating system
Affected:< 10.0.17763.9020
Windows 10 21h2Operating system
Affected:< 10.0.19044.7548
Windows 10 22h2Operating system
Affected:< 10.0.19045.7548
Windows 11 24h2Operating system
Affected:< 10.0.26100.8875
Windows 11 25h2Operating system
Affected:< 10.0.26200.8875
Windows 11 26h1Operating system
Affected:< 10.0.28000.2525
Windows Server 2016Operating system
Affected:< 10.0.14393.9339

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. Check Windows build version
    Run 'systeminfo' or 'winver' from command prompt and note the OS Version and Build number
    Affected if The build number falls below the threshold for your Windows edition (see version-specific thresholds)
  2. Identify exact Windows edition
    Run 'systeminfo' and check the OS Name field to determine if you are running Windows 10 1607, 1809, 21h2, 22h2, Windows 11 24h2/25h2/26h1, or Windows Server 2016
    Affected if You are running any of the affected editions listed in the CVE
  3. Compare against version thresholds
    For Windows 10 1607/Server 2016: verify build < 10.0.14393.9339. For Windows 10 1809: verify build < 10.0.17763.9020. For Windows 10 21h2: verify build < 10.0.19044.7548. For Windows 10 22h2: verify build < 10.0.19045.7548. For Windows 11 24h2: verify build < 10.0.26100.8875. For Windows 11 25h2: verify build < 10.0.26200.8875. For Windows 11 26h1: verify build < 10.0.28000.2525
    Affected if Your installed build number is less than the threshold for your specific Windows edition

You are affected if your Windows build number is lower than the threshold corresponding to your Windows edition (1607, 1809, 21h2, 22h2, 24h2, 25h2, 26h1, or Server 2016).

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.9339 / 10.0.17763.9020 / 10.0.19044.7548 or later
Fixed in 10.0.14393.933910.0.17763.902010.0.19044.7548
Interim mitigation

Apply vendor-supplied Windows security patches promptly. As this is a kernel-level vulnerability requiring local access, prioritize patch deployment to workstations and servers with direct user access, and follow least-privilege principles to limit exposure.

Recommended fix High confidence

Install the corresponding Windows security update (KB patch) that addresses this vulnerability - the specific KB number can be obtained from Microsoft's Security Update Guide at msrc.microsoft.com for CVE-2026-50377

  1. Open Windows Update on the affected system (Settings > Update & Security > Windows Update)
  2. Click 'Check for updates' to ensure you receive the latest patches
  3. Install any available security updates, particularly those released after the affected version thresholds
  4. Restart the system to apply the kernel-level updates
  5. Verify the installed version matches or exceeds the fixed release: Windows 10 1607/Server 2016: 10.0.14393.9339, Windows 10 1809: 10.0.17763.9020, Windows 10 21h2: 10.0.19044.7548, Windows 10 22h2: 10.0.19045.7548, Windows 11 24h2: 10.0.26100.8875, Windows 11 25h2: 10.0.26200.8875, Windows 11 26h1: 10.0.28000.2525
Caveat Standard Windows update risks apply (potential for compatibility issues with legacy software; test in staging environment before broad deployment)

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
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50377 — 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-50377 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