dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2026-50503

HIGH · 7.0 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.26100.8875 / 10.0.26100.33158 or later.
See remediation →
72/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
Concurrent 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
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 race condition vulnerability exists in Windows Runtime where concurrent execution with shared resources lacks proper synchronization. This allows an authorized local attacker to exploit the timing window and elevate their privileges on the affected system.

MitigationApply vendor-supplied patches for Windows Runtime when available. Until then, limit local user privileges and monitor for suspicious 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 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 2025Operating system
Affected:< 10.0.26100.33158

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Windows version and build number
    Run 'winver' from command prompt or check System Properties to see the OS name and version number
    Affected if The system runs Windows 11 24h2, 25h2, 26h1, or Windows Server 2025 and the build number is below the fixed versions (26100.8875, 26200.8875, 28000.2525, or 26100.33158 respectively)
  2. Confirm exact build with systeminfo
    Run 'systeminfo' from an elevated command prompt and locate the 'OS Version' line showing the full build number (e.g., 10.0.26100.xxxx)
    Affected if The displayed build number is lower than the fixed thresholds for the detected Windows edition
  3. Verify Windows edition matches affected list
    Run 'winver' or check 'systeminfo' to confirm the specific edition (Windows 11 24h2, 25h2, 26h1, or Windows Server 2025)
    Affected if The installed edition is one of the four affected versions and the build falls below the corresponding threshold
  4. Check for recent Windows Updates
    Open Settings > Windows Update > Update history and look for recent security updates related to Windows Runtime
    Affected if No recent patches addressing this vulnerability have been installed and the version remains in the vulnerable range

The system is affected if it runs Windows 11 24h2, 25h2, 26h1, or Windows Server 2025 with a build number lower than 26100.8875, 26200.8875, 28000.2525, or 26100.33158 respectively.

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.26100.8875 / 10.0.26100.33158 / 10.0.26200.8875 or later
Fixed in 10.0.26100.887510.0.26100.3315810.0.26200.8875
Interim mitigation

Apply vendor-supplied patches for Windows Runtime when available. Until then, limit local user privileges and monitor for suspicious process activity.

Recommended fix High confidence

Windows 11 24h2: version 10.0.26100.8875 or later | Windows 11 25h2: version 10.0.26200.8875 or later | Windows 11 26h1: version 10.0.28000.2525 or later | Windows Server 2025: version 10.0.26100.33158 or later

  1. Open Windows Settings and navigate to Windows Update
  2. Check for updates and install any available security updates
  3. Alternatively, manually download and install the appropriate KB update for your Windows version from the Microsoft Update Catalog
  4. Restart the system after installing the update
  5. Verify the installation by checking the Windows version (winver) matches or exceeds: 10.0.26100.8875 for Windows 11 24h2, 10.0.26200.8875 for Windows 11 25h2, 10.0.28000.2525 for Windows 11 26h1, or 10.0.26100.33158 for Windows Server 2025
Caveat Standard Windows update; review release notes for any known compatibility issues before deploying in enterprise environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 11 24h2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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