dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50311

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
Improper access control in Windows Server 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 in Windows Server enables an authenticated user to escalate privileges locally to a higher integrity level, likely through manipulation of object permissions, service configurations, or token handling.

MitigationApply Microsoft security updates for Windows Server when released; enforce least-privilege principles; audit user group memberships and service account permissions.

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 command prompt or check System Properties, or run 'systeminfo' and look at OS Name and OS Version fields
    Affected if Version or build number falls within the affected ranges listed below
  2. Check if running Windows Server 2012 or R2
    Run 'systeminfo' and look for 'Server' in the OS Name field; check if version indicates 2012
    Affected if System is Windows Server 2012 or Windows Server 2012 R2 (all versions affected)
  3. Verify Windows 10 1607 build
    Run 'winver' or check systeminfo; look for build number 10.0.14393.9339 or lower
    Affected if Build is less than 10.0.14393.9339 on Windows 10 1607
  4. Verify Windows 10 1809 build
    Check build number; affected if less than 10.0.17763.9020
    Affected if Build is less than 10.0.17763.9020 on Windows 10 version 1809
  5. Verify Windows 10 21h2 and 22h2 builds
    Check build number against 10.0.19044.7548 (21h2) or 10.0.19045.7548 (22h2)
    Affected if Build is less than 10.0.19044.7548 on 21h2, or less than 10.0.19045.7548 on 22h2
  6. Verify Windows 11 builds
    Check build number: 24h2 < 10.0.26100.8875, 25h2 < 10.0.26200.8875, 26h1 < 10.0.28000.2269 or < 10.0.28000.2525
    Affected if Build is below the specified threshold for the installed Windows 11 version

System is affected if running any Windows version with a build number below the specified threshold, or if running Windows Server 2012/R2 (all versions), and the system allows authenticated users to interact with the vulnerable access control mechanism.

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 updates for Windows Server when released; enforce least-privilege principles; audit user group memberships and service account permissions.

Recommended fix High confidence

Windows 10 1607 -> 10.0.14393.9339 or later | 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.

  1. Open Microsoft Update Catalog (catalog.update.microsoft.com) and search for the relevant security update for your Windows version
  2. Install the appropriate monthly security update (KB) that addresses this vulnerability - check Windows Update or Microsoft Update Catalog for the latest security patches
  3. Restart the system after applying the update
  4. Verify the update installed successfully by checking installed updates in Control Panel > Programs and Features > View installed updates
  5. For Windows Server 2012/2012 R2: These versions are End of Support (EOS) as of October 2023. Microsoft may still provide extended security updates (ESU) for eligible organizations, or migration to a supported Windows Server version is strongly recommended
Caveat Windows Server 2012/2012 R2 is End of Support - no free security updates available; requires Microsoft Extended Security Updates (ESU) program enrollment or migration to supported OS version

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
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,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 $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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