dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50673

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
Null pointer dereference 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 null pointer dereference vulnerability exists in the Windows Kernel that allows a locally authorized attacker to elevate their privileges to a higher level. Null pointer dereference flaws occur when the kernel attempts to dereference a NULL pointer that it has not properly validated, potentially leading to a crash or controlled memory corruption that can be exploited for privilege escalation.

MitigationApply Microsoft security patches for Windows Kernel vulnerabilities through Windows Update. Until the official patch is available, monitor for suspicious kernel-mode activity and restrict local administrative access to trusted personnel only.

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.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. Check Windows build number
    Run 'winver' from command prompt or check 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to display the installed Windows version and build number
    Affected if The build number falls below the thresholds: 14393.9339 (1607), 17763.9020 (1809), 19044.7548 (21h2), 19045.7548 (22h2), 26100.8875 (24h2), 26200.8875 (25h2), or 28000.2525 (26h1)
  2. Confirm Windows 10 release
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' and 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v UBR' to get the full build number (CurrentBuild.UBR)
    Affected if The combined build number (CurrentBuild.UBR) is lower than the version-specific threshold for your Windows 10 release
  3. Identify Windows 11 version
    Check 'systeminfo' output for the exact Windows 11 version (24h2, 25h2, or 26h1) and its corresponding build number
    Affected if Running Windows 11 24h2 with build below 26100.8875, 25h2 below 26200.8875, or 26h1 below 28000.2525
  4. Check Windows Server 2012 variant
    Run 'systeminfo | findstr "Windows Server"' to identify if the system is Windows Server 2012 or Windows Server 2012 R2
    Affected if The system is any version of Windows Server 2012 or Windows Server 2012 R2 (all versions are affected per the advisory)
  5. Verify kernel version as secondary check
    Run 'ver' command to display the Windows version string or check the file version of 'ntoskrnl.exe' in 'C:\Windows\System32\ntoskrnl.exe'
    Affected if The kernel version string indicates a build number below the patched thresholds for the respective Windows release

The system is affected if it runs any Windows 10 version below the specified build thresholds, Windows 11 24h2/25h2/26h1 below their thresholds, or any Windows Server 2012/R2 variant.

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 Kernel vulnerabilities through Windows Update. Until the official patch is available, monitor for suspicious kernel-mode activity and restrict local administrative access to trusted personnel only.

Recommended fix High confidence

Upgrade to 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; W

  1. Identify the current Windows version and build by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which version category applies (Windows 10 1607, 1809, 21h2, 22h2, Windows 11 24h2/25h2/26h1, or Windows Server 2012/2012 R2)
  3. For Windows 10: Navigate to Settings > Update & Security > Windows Update and check for updates
  4. For Windows 11: Navigate to Settings > Windows Update and check for updates
  5. For Windows Server: Use Windows Update, WSUS, or download the specific update from Microsoft Catalog
  6. Ensure the installed build number meets or exceeds the fixed version for your product line
  7. Reboot the system after applying updates
  8. Verify the fix by checking the build number again and confirming it matches or exceeds: 14393.9339 (1607), 17763.9020 (1809), 19044.7548 (21h2), 19045.7548 (22h2), 26100.8875 (24h2), 26200.8875 (25h2), 28000.2525 (26h1)
Caveat Standard Windows update risks apply - ensure backups exist and test compatibility with critical applications before deploying broadly; Windows Server 2012/R2 is end-of-support and Microsoft recommends migrating to newer OS 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
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA3.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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