dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2026-50670

HIGH · 7.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.17763.9020 / 10.0.19044.7548 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 · low confidence

Out-of-bounds read vulnerability in the Windows Kernel enables a local authenticated attacker to read unintended memory contents, which can be leveraged to escalate privileges to higher integrity levels.

MitigationApply Microsoft security updates for Windows Kernel once released; prioritize patching endpoints with local user access.

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 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 2019Operating system
Affected:< 10.0.17763.9020
Windows Server 2022Operating system
Affected:< 10.0.20348.5386

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 number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to display the installed Windows version and build number
    Affected if the displayed build number is lower than the fixed version for your Windows release
  2. Identify Windows release version
    Note the Windows release name (such as 1809, 21h2, 22h2, 24h2, 25h2, 26h1) shown in winver or the Windows settings under System > About
    Affected if the release version matches one of the affected products listed in the CVE
  3. Compare against CVE version thresholds
    Cross-reference your confirmed build number with the fixed version thresholds: 10.0.17763.9020 (1809/Server 2019), 10.0.19044.7548 (21h2), 10.0.19045.7548 (22h2), 10.0.26100.8875 (24h2), 10.0.26200.8875 (25h2), 10.0.28000.2525 (26h1), or 10.0.20348.5386 (Server 2022)
    Affected if your build number falls below the threshold for your specific Windows release

You are affected if your Windows version and build number are below the fixed version thresholds listed for your Windows release, and you have local authenticated user access to the system.

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.17763.9020 / 10.0.19044.7548 / 10.0.19045.7548 or later
Fixed in 10.0.17763.902010.0.19044.754810.0.19045.7548
Interim mitigation

Apply Microsoft security updates for Windows Kernel once released; prioritize patching endpoints with local user access.

Recommended fix High confidence

Windows 10 1809: 10.0.17763.9020 or later | Windows 10 21h2: 10.0.19044.7548 or later | Windows 10 22h2: 10.0.19045.7548 or later | Windows 11 24h2: 10.0.26100.8875 or later | Windows 11 25h2: 10.0.26200.8875 or later | Windows 11 26h1: 10.0.28000.2525 or later | Windows Server 2019: 10.0.17763.9020

  1. 1. Identify the current Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine which affected version category applies to your system (Windows 10 1809/21h2/22h2, Windows 11 24h2/25h2/26h1, Server 2019, or Server 2022)
  3. 3. Back up critical data before applying updates
  4. 4. Apply Windows Updates via Settings > Update & Security > Windows Update, or use Windows Server Update Services (WSUS) for server environments
  5. 5. Alternatively, download and install the specific security update from the Microsoft Update Catalog matching your OS version and build
  6. 6. Restart the system after the update is installed
  7. 7. Verify the build number matches or exceeds the fixed version: 10.0.17763.9020, 10.0.19044.7548, 10.0.19045.7548, 10.0.26100.8875, 10.0.26200.8875, 10.0.28000.2525, or 10.0.20348.5386
Caveat Standard Windows update risks apply; test in staging environment before production deployment

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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