dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2026-54112

HIGH · 7.0 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 →
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 · moderate confidence

A race condition vulnerability exists in Windows Win32K (kernel-mode graphics subsystem) where concurrent execution with improper synchronization allows an authorized attacker to elevate privileges locally to higher integrity levels.

MitigationApply Microsoft security updates for this vulnerability through Windows Update or enterprise patch management systems. This is a local privilege escalation requiring authenticated local access.

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
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 10 build version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' and note the build number (e.g., 10.0.17763.xxxx for 1809)
    Affected if Running Windows 10 1809 (build < 10.0.17763.9020), 21h2 (build < 10.0.19044.7548), or 22h2 (build < 10.0.19045.7548)
  2. Check Windows 11 build version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' and note the build number (e.g., 10.0.26100.xxxx for 24h2)
    Affected if Running Windows 11 24h2 (build < 10.0.26100.8875), 25h2 (build < 10.0.26200.8875), or 26h1 (build < 10.0.28000.2525)
  3. Check Windows Server build version
    Run 'systeminfo' or 'winver' on Windows Server and note the build number (e.g., 10.0.17763.xxxx for Server 2019)
    Affected if Running Windows Server 2019 (build < 10.0.17763.9020) or Windows Server 2022 (build < 10.0.20348.5386)
  4. Verify Win32K subsystem presence
    This vulnerability exists in the Win32K.sys kernel component - confirm system is a standard Windows installation with graphics capabilities (default on all listed affected versions)
    Affected if System has Win32K.sys present (all standard Windows installations) and version falls below thresholds in steps 1-3

You are affected if your Windows version (10, 11, or Server) has a build number lower than the thresholds listed for your specific release branch, and the Win32K graphics subsystem is present (default configuration).

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.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 this vulnerability through Windows Update or enterprise patch management systems. This is a local privilege escalation requiring authenticated local access.

Recommended fix High confidence

Install the appropriate Windows cumulative update containing the fix for CVE-2026-54112, targeting build 10.0.17763.9020+ for Windows 10 1809/Server 2019, 10.0.19044.7548+ for Windows 10 21H2, 10.0.19045.7548+ for Windows 10 22H2, 10.0.26100.8875+ for Windows 11 24H2, 10.0.26200.8875+ for Windows 11

  1. 1. Identify the exact Windows version currently installed by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine which fixed build number applies to your Windows edition from the reference: Windows 10 1809/Server 2019 requires 10.0.17763.9020 or later, Windows 10 21H2 requires 10.0.19044.7548 or later, Windows 10 22H2 requires 10.0.19045.7548 or later, Windows 11 24H2 requires 10.0.26100.8875 or later, Windows 11 25H2 requires 10.0.26200.8875 or later, Windows 11 26H1 requires 10.0.28000.2525 or
  3. 3. Open Settings > Windows Update > Check for updates, or use WSUS/SCCM for enterprise deployments
  4. 4. Download and install all available cumulative updates until your build meets or exceeds the required fixed version
  5. 5. Restart the system when prompted to complete the installation
  6. 6. Verify the update was successful by running 'winver' and confirming the build number matches or exceeds the fixed version for your Windows edition
Caveat Standard Windows cumulative update apply; no major breaking changes expected for this privilege escalation patch, though as with all updates, test in a staging environment before broad deployment

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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 locally
dbcve dependency scanner

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