dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50390

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
Access of resource using incompatible type ('type confusion') 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 · high confidence

Type confusion vulnerability in the Windows Kernel allows a locally authenticated attacker to manipulate resource handling to elevate privileges to SYSTEM level by exploiting incompatible type access within kernel-mode code.

MitigationDeploy the Microsoft security update for CVE-2026-50390 via Windows Update or WSUS to all affected Windows systems; this kernel-level flaw requires Microsoft's patch to remediate.

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.2269< 10.0.28000.2525
Windows Server 2012Operating system
Affected:all versions= r2

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. Identify Windows version and build number
    Run 'winver' from the Run dialog or execute 'systeminfo' in Command Prompt and locate the OS Name and Version lines
    Affected if The displayed build number falls below the safe version thresholds listed for your Windows release (e.g., 10.0.14393.9339 for Windows 10 1607, 10.0.17763.9020 for Windows 10 1809, etc.)
  2. Confirm Windows 10 release
    Run 'winver' and note the specific release (1607, 1809, 21h2, or 22h2) shown in the dialog
    Affected if The release matches 1607, 1809, 21h2, or 22h2 and the build number is below the corresponding threshold for that release
  3. Confirm Windows 11 release
    Run 'winver' or check System Properties to identify if the system runs Windows 11 24h2, 25h2, or 26h1
    Affected if The system runs Windows 11 24h2 (build < 10.0.26100.8875), 25h2 (build < 10.0.26200.8875), or 26h1 (build < 10.0.28000.2269 or < 10.0.28000.2525)
  4. Check if running Windows Server 2012 or R2
    Run 'systeminfo' and examine the OS Name field for 'Windows Server 2012' or 'Windows Server 2012 R2'
    Affected if The system is Windows Server 2012 (any version) or Windows Server 2012 R2, as these are listed as affected for all versions

The system is affected if it runs any of the listed Windows 10 or 11 versions below the safe build thresholds, or if it is any version of Windows Server 2012/R2.

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

Deploy the Microsoft security update for CVE-2026-50390 via Windows Update or WSUS to all affected Windows systems; this kernel-level flaw requires Microsoft's patch to remediate.

Recommended fix High confidence

Windows 10 1607: build 10.0.14393.9339 or later | Windows 10 1809: build 10.0.17763.9020 or later | Windows 10 21h2: build 10.0.19044.7548 or later | Windows 10 22h2: build 10.0.19045.7548 or later | Windows 11 24h2: build 10.0.26100.8875 or later | Windows 11 25h2: build 10.0.26200.8875 or later |

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which version range your current build falls into from the affected versions list
  3. Apply the appropriate Windows Security Update that corresponds to your version, or upgrade to the minimum fixed build number for your release
  4. For Windows Server 2012/2012 R2: Microsoft has ended extended support; migrate to a supported Windows Server version as no security patch is available
  5. After patching, verify the build number has updated to or past the fixed version using 'winver'
Caveat Windows Server 2012 and 2012 R2 have no security patch available due to end of support; requires migration to newer Windows Server version. Standard Windows update best practices apply for other versions.

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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