dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2026-54125

HIGH · 7.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.17763.9020 / 10.0.19044.7548 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
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 of code accesses shared resources without proper synchronization. An authorized local attacker can exploit this improper synchronization to elevate privileges to a higher level, potentially gaining administrative or SYSTEM-level access on the affected Windows system.

MitigationApply Microsoft security updates for Windows Runtime when available; restrict local user privileges where possible and monitor for suspicious process activity indicating privilege escalation attempts.

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 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 2019Operating system
Affected:< 10.0.17763.9020
Windows Server 2022Operating system
Affected:< 10.0.20348.5386

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. Identify Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'. Alternatively, run 'ver' in cmd or '[System.Environment]::OSVersion.Version' in PowerShell to get the build number.
    Affected if The installed build number falls below any of these thresholds: 10.0.17763.9020, 10.0.19044.7548, 10.0.19045.7548, 10.0.26100.8875, 10.0.26200.8875, 10.0.28000.2525, or 10.0.20348.5386 depending on your Windows edition and release.
  2. Confirm Windows 10/11 or Windows Server edition
    Run 'systeminfo' in Command Prompt and look at the OS Name field to determine if you are running Windows 10 (1809, 21h2, or 22h2), Windows 11 (24h2, 25h2, or 26h1), Windows Server 2019, or Windows Server 2022.
    Affected if The system is running any of the affected Windows editions and versions listed in the CVE, and the build number is below the corresponding fixed version.
  3. Check current user privilege context
    Run 'whoami /priv' or 'whoami /all' in Command Prompt to see your current privilege level. This helps determine if you are running as a standard user who could potentially be elevated, or as an administrator already.
    Affected if You are running as a standard (non-admin) user on an affected system; the vulnerability would allow privilege escalation to admin or SYSTEM.
  4. Review installed Windows updates
    Open Settings > Windows Update > Update history, or run 'Get-HotFix' in PowerShell to list installed updates. Look for recent security updates related to Windows Runtime or privilege escalation fixes.
    Affected if The system is missing security updates that address this vulnerability; no relevant Windows Runtime or privilege escalation patch is installed.

A system is affected if it runs any of the specified Windows 10, Windows 11, or Windows Server versions with a build number lower than the fixed threshold for that release, and the attacker has local access to execute code.

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.

From vendor data
Upgrade available Upgrade to 10.0.17763.9020 / 10.0.19044.7548 / 10.0.19045.7548 or later
Fixed in 10.0.17763.902010.0.19044.754810.0.19045.7548
Interim mitigation

Apply Microsoft security updates for Windows Runtime when available; restrict local user privileges where possible and monitor for suspicious process activity indicating privilege escalation attempts.

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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