dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-54107

HIGH · 7.0 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.14393.9339 / 10.0.17763.9020 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 Win32K 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 · high confidence

A race condition vulnerability exists in Windows Win32K (the kernel-mode graphics subsystem) where improper synchronization of shared resources allows a locally authorized attacker to elevate privileges to higher permissions.

MitigationApply the Microsoft security update for CVE-2026-54107 via Windows Update or enterprise patch management systems; monitor for any Microsoft-issued workaround guidance while awaiting the patch.

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 1607Operating system
Affected:< 10.0.14393.9339
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 2012Operating system
Affected:all versions= r2

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. Check Windows version using winver command
    Open Command Prompt and run `winver`. Note the full version number displayed (e.g., 10.0.19045.xxxx).
    Affected if The displayed build number is lower than 10.0.14393.9339 (Windows 10 1607), 10.0.17763.9020 (Windows 10 1809), 10.0.19044.7548 (Windows 10 21h2), 10.0.19045.7548 (Windows 10 22h2), 10.0.26100.8875 (Windows 11 24h2), 10.0.26200.8875 (Windows 11 25h2), or 10.0.28000.2525 (Windows 11 26h1).
  2. Check Windows Server version using systeminfo
    Run `systeminfo` in Command Prompt and locate the "OS Version" field. For Server 2012/R2, note the full build number.
    Affected if Running Windows Server 2012 or Windows Server 2012 R2 (any version) since these are listed as all versions affected.
  3. Confirm Win32K subsystem is present
    This is a kernel-level component present by default on all supported Windows installations. No specific command needed - if Windows is running, Win32K.sys is loaded.
    Affected if System is running any Windows desktop or server OS - the vulnerability exists in the Win32K graphics subsystem which is a core component.
  4. Cross-reference build number with CVE thresholds
    Compare your exact build number (from step 1 or 2) against the specific threshold versions listed in the CVE: 14393.9339, 17763.9020, 19044.7548, 19045.7548, 26100.8875, 26200.8875, or 28000.2525.
    Affected if Your installed build number is LESS THAN the threshold for your specific Windows version/release.

You are affected if your Windows version build number is lower than the threshold listed for your specific Windows release, or if you are running any version of Windows Server 2012/R2.

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.14393.9339 / 10.0.17763.9020 / 10.0.19044.7548 or later
Fixed in 10.0.14393.933910.0.17763.902010.0.19044.7548
Interim mitigation

Apply the Microsoft security update for CVE-2026-54107 via Windows Update or enterprise patch management systems; monitor for any Microsoft-issued workaround guidance while awaiting the patch.

Recommended fix High confidence

Upgrade to Windows 10 1607 build 10.0.14393.9339, Windows 10 1809 build 10.0.17763.9020, Windows 10 21h2 build 10.0.19044.7548, Windows 10 22h2 build 10.0.19045.7548, Windows 11 24h2 build 10.0.26100.8875, Windows 11 25h2 build 10.0.26200.8875, or Windows 11 26h1 build 10.0.28000.2525; Windows Serve

  1. Open Windows Settings and navigate to Windows Update
  2. Check for and install the latest Windows security updates
  3. Alternatively, manually download and install the appropriate Cumulative Update for your Windows version from the Microsoft Update Catalog
  4. Verify the update was installed successfully by checking Windows Update history
  5. Restart the system if prompted to complete the installation
  6. Confirm the system build number matches or exceeds the fixed version for your Windows release
Caveat Windows Server 2012 R2 is end-of-support; upgrading may require application compatibility testing; ensure backups before updating

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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