CVE-2026-50378
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 · uneditedConcurrent execution using shared resource with improper synchronization ('race condition') in Windows Key Guard 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 · moderate confidenceA race condition vulnerability exists in Windows Key Guard where improper synchronization of shared resources allows an authorized local attacker to exploit concurrent execution and elevate privileges to higher permission levels.
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.17763.9020< 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.17763.9020< 10.0.20348.5386CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows version against affected rangesRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify your Windows version and build numberAffected if The build number is below 17763.9020 (Win 10 1809/Server 2019), 19044.7548 (Win 10 21h2), 19045.7548 (Win 10 22h2), 26100.8875 (Win 11 24h2), 26200.8875 (Win 11 25h2), 28000.2269 or 28000.2525 (Win 11 26h1), or 20348.5386 (Server 2022)
-
Verify Windows Update statusOpen Settings > Windows Update and check for pending updates, or run 'powershell Get-HotFix' to list installed security updatesAffected if No recent security updates have been installed matching or exceeding the fixed build numbers listed above
-
Review user account privilegesRun 'whoami /all' to list current user privileges and group membershipsAffected if The current user has administrative privileges or is a member of privileged groups (Administrators, Backup Operators, etc.), providing the attacker with elevated access to target
-
Audit local user accounts for suspicious changesRun 'net user' to list all local accounts, then check Event Viewer Security logs (Event ID 4720 for account creation, 4722 for account enablement, 4728 for member added to security group)Affected if New local accounts or unexpected group memberships appear that were not authorized
-
Check for suspicious processes or privilege escalation toolsRun 'tasklist' and review running processes for unfamiliar executables, or use 'wmic process get name,processid,commandline' to inspect process command linesAffected if Unknown processes are running, particularly those associated with privilege escalation or credential dumping
You are affected if your Windows build number is below the fixed versions listed AND an untrusted local user could potentially execute concurrent code against Windows Key Guard functionality.
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.17763.902010.0.19044.754810.0.19045.7548
Apply available Microsoft security updates for Windows Key Guard when released; until then, limit local administrative access and monitor for suspicious process activity.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50378 — 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-50378 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