dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50354

HIGH · 7.1 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 →
73/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
Use after free 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

A use-after-free vulnerability exists in the Windows Kernel where memory is accessed after being freed, allowing a locally authenticated attacker to elevate privileges to kernel level. The vulnerability stems from improper memory management in kernel-mode components, enabling arbitrary code execution with elevated system privileges.

MitigationApply Microsoft security patches for this kernel vulnerability once available; until then, restrict local user privileges and monitor for suspicious kernel-level process activity.

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 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
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact Windows edition and build number
    Affected if The build number falls below the fixed version for your Windows edition (e.g., below 10.0.14393.9339 for Windows 10 1607/Server 2016, below 10.0.17763.9020 for Windows 10 1809, etc.)
  2. Confirm Windows edition matches affected list
    Check if the system is Windows 10 1607, 1809, 21h2, 22h2, Windows 11 24h2, 25h2, 26h1, or Windows Server 2016 using 'systeminfo' output
    Affected if The installed Windows edition is one of those listed in the affected products but the build number is below the patched version for that edition
  3. Verify kernel version is unpatched
    Run 'winver' to display the full version string (e.g., 10.0.19044.7548) and compare it against the fixed build numbers for your specific Windows release
    Affected if The displayed build version is lower than the minimum fixed version for your Windows release

A system is affected if it runs any of the listed Windows versions (10 1607, 1809, 21h2, 22h2, 11 24h2, 25h2, 26h1, or Server 2016) AND its build number is below the corresponding patched version for that release.

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 this kernel vulnerability once available; until then, restrict local user privileges and monitor for suspicious kernel-level process activity.

Recommended fix High confidence

Upgrade to the latest Windows security update containing the fix; threshold versions are: 10.0.14393.9339 (Windows 10 1607/Server 2016), 10.0.17763.9020 (Windows 10 1809), 10.0.19044.7548 (Windows 10 21h2), 10.0.19045.7548 (Windows 10 22h2), 10.0.26100.8875 (Windows 11 24h2), 10.0.26200.8875 (Window

  1. Check current Windows version by running `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"`
  2. Open Settings > Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest security updates
  4. Restart the computer when prompted to complete the installation
  5. Verify the patch is installed by checking the Windows version matches or exceeds: 10.0.14393.9339 (Windows 10 1607/Server 2016), 10.0.17763.9020 (Windows 10 1809), 10.0.19044.7548 (Windows 10 21h2), 10.0.19045.7548 (Windows 10 22h2), 10.0.26100.8875 (Windows 11 24h2), 10.0.26200.8875 (Windows 11 25h2), or 10.0.28000.2525 (Windows 11 26h1)
  6. Alternatively, manually install the specific KB patch from Microsoft Update Catalog matching your Windows version
Caveat Standard Windows update risks apply: update may require restart, potential for compatibility issues with legacy software; test critical applications before broad deployment in production environments

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
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
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,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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