CVE-2026-50385
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 Runtime 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 Runtime where improper synchronization of shared resources allows an authorized local attacker to elevate privileges. The vulnerability stems from concurrent execution issues that can be exploited to gain higher-level access than initially granted.
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.26100.8875< 10.0.26200.8875< 10.0.28000.2269< 10.0.28000.2525< 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 11 24h2 build versionRun `winver` or `systeminfo | findstr /C:"Build Number"` and verify the version is below 10.0.26100.8875Affected if Running Windows 11 24h2 with build version less than 26100.8875
-
Check Windows 11 25h2 build versionRun `winver` or `systeminfo | findstr /C:"Build Number"` and verify the version is below 10.0.26200.8875Affected if Running Windows 11 25h2 with build version less than 26200.8875
-
Check Windows 11 26h1 build versionRun `winver` or `systeminfo | findstr /C:"Build Number"` and verify the version is below 10.0.28000.2269 or between 10.0.28000.2269 and 10.0.28000.2524Affected if Running Windows 11 26h1 with build version less than 28000.2525 (including versions 28000.2269-28000.2524)
-
Check Windows Server 2025 build versionRun `winver` or `systeminfo | findstr /C:"Build Number"` on the server and verify the version is below 10.0.26100.33158Affected if Running Windows Server 2025 with build version less than 26100.33158
The environment is affected if running any of the listed Windows 11 versions or Windows Server 2025 with a build number below the specified threshold for that release channel.
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.26100.887510.0.26100.3315810.0.26200.8875
Apply Microsoft security patches for Windows Runtime when available; prioritize patching systems with user-level access that could be leveraged for privilege escalation.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50385 — 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-50385 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