dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50325

HIGH · 7.0 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 →
72/100
Remediation priority · Elevated
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
Improper access control in Windows Win32K 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

Improper access control vulnerability in Windows Win32K (kernel-mode graphics subsystem) enables a locally authenticated attacker to elevate privileges to higher integrity levels. The vulnerability requires the attacker to have some form of authorized access to the target system prior to exploitation.

MitigationApply Microsoft security patches for Windows Win32K when released; prioritize patching systems with higher privilege access vectors and ensure least-privilege principles are enforced for local accounts.

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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 installed Windows version and build number
    Run 'winver' from command prompt or use 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to display the full version string including build number
    Affected if The displayed build number falls below the thresholds for your Windows version (e.g., below 14393.9339 for Windows 10 1607, below 17763.9020 for Windows 10 1809, etc.)
  2. Confirm Windows edition family
    Run 'systeminfo' and note whether the system is Windows 10, Windows 11, or Windows Server 2012. Also verify the specific release (such as 1607, 1809, 21h2, 22h2, 24h2, 25h2, 26h1) from the version string
    Affected if The system runs an affected Windows 10 release, Windows 11 release, or Windows Server 2012/2012 R2 regardless of build number
  3. Obtain exact build number programmatically
    Run 'powershell -Command "(Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion').CurrentBuild"' to retrieve the numeric build, and '(Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion').UBR' for the revision number
    Affected if The combined build (CurrentBuild.UBR) is lower than the affected version thresholds for the detected Windows release

You are affected if your installed Windows version matches one of the listed families (Windows 10 1607/1809/21h2/22h2, Windows 11 24h2/25h2/26h1, or Windows Server 2012/R2) AND your specific build number is below the corresponding threshold, or if you are on Windows Server 2012/R2 at any version.

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 Microsoft security patches for Windows Win32K when released; prioritize patching systems with higher privilege access vectors and ensure least-privilege principles are enforced for local accounts.

Recommended fix High confidence

Upgrade to the specific build numbers listed (10.0.14393.9339, 10.0.17763.9020, 10.0.19044.7548, 10.0.19045.7548, 10.0.26100.8875, 10.0.26200.8875, or 10.0.28000.2525 depending on version); for Windows Server 2012/R2 migrate to supported Windows Server version

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo' in command prompt
  2. For Windows 10 1607: Upgrade to build 10.0.14393.9339 or later via Windows Update or Media Creation Tool
  3. For Windows 10 1809: Upgrade to build 10.0.17763.9020 or later via Windows Update or Media Creation Tool
  4. For Windows 10 21h2: Upgrade to build 10.0.19044.7548 or later via Windows Update or Media Creation Tool
  5. For Windows 10 22h2: Upgrade to build 10.0.19045.7548 or later via Windows Update or Media Creation Tool
  6. For Windows 11 24h2: Upgrade to build 10.0.26100.8875 or later via Windows Update
  7. For Windows 11 25h2: Upgrade to build 10.0.26200.8875 or later via Windows Update
  8. For Windows 11 26h1: Upgrade to build 10.0.28000.2525 or later via Windows Update
Caveat Windows Server 2012/R2 has no patch; end-of-life migration required; ensure application compatibility before upgrading client Windows versions

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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