CVE-2026-50423
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 · uneditedImproper access control in Windows Kernel allows an authorized attacker to elevate privileges locally.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
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 confidenceThis is a local privilege escalation vulnerability in the Windows Kernel caused by improper access control. An authorized attacker with local access can exploit this kernel-level flaw to elevate their privileges beyond their current authorized permissions, potentially gaining administrator or SYSTEM-level access.
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< 10.0.19044.7548< 10.0.19045.7548< 10.0.26100.8875< 10.0.26200.8875< 10.0.28000.2269< 10.0.28000.2525< 10.0.20348.5386< 10.0.26100.33158CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows build versionRun 'winver' from command prompt or 'systeminfo' and locate the 'OS Build' or 'Build' number in the outputAffected if The build number is lower than the affected versions: 19044.7548 (Win10 21h2), 19045.7548 (Win10 22h2), 26100.8875 (Win11 24h2), 26200.8875 (Win11 25h2), 28000.2269/28000.2525 (Win11 26h1), 20348.5386 (Server 2022), or 26100.33158 (Server 2025)
-
Verify Windows edition and releaseRun 'winver' to confirm the exact Windows edition (e.g., Windows 10 21h2, Windows 11 24h2, Windows Server 2022) and match it to the corresponding build number from step 1Affected if The edition matches an affected product line and its build falls below the specified threshold for that release
-
Check CurrentVersion registry keyOpen Registry Editor and navigate to 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion', then review the 'CurrentBuild' and 'DisplayVersion' valuesAffected if The CurrentBuild number is less than the affected build threshold for your Windows release
-
Confirm kernel version (optional verification)Run 'kernel32.dll' version check via 'powershell (Get-Item C:\Windows\System32\kernel32.dll).VersionInfo' or check 'systeminfo' for 'Kernel Version'Affected if The kernel version corresponds to an unpatched build that falls within the affected ranges
You are affected if your Windows version build number is lower than the threshold listed for your specific Windows release (10/11/Server) and you have not applied the relevant Microsoft security patch for this kernel privilege escalation vulnerability.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data10.0.19044.754810.0.19045.754810.0.20348.5386
Apply the relevant Microsoft security patch for this kernel vulnerability through standard Windows Update or manual KB deployment, followed by system reboot and verification of privilege separation controls.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50423 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-50423 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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