dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2026-54111

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 USB Print Driver 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 the Windows USB Print Driver where improper synchronization of shared resources allows an authorized local attacker to elevate privileges. The vulnerability stems from concurrent access to shared resources without proper locking mechanisms in the print driver, enabling an attacker who already has local access to exploit the timing window and gain higher privileges.

MitigationApply the Microsoft security patch for CVE-2026-54111 once released. Until then, limit local access to trusted users only and monitor for suspicious USB device interactions.

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.2269< 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. Check Windows version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to retrieve the exact Windows build. Alternatively, check the registry key HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion for the BuildLabEx or CurrentBuildNumber value.
    Affected if The build number is less than 10.0.26100.8875 on Windows 11 24h2, less than 10.0.26200.8875 on Windows 11 25h2, less than 10.0.28000.2269 or 10.0.28000.2525 on Windows 11 26h1, or less than 10.0.26100.33158 on Windows Server 2025.
  2. Verify USB Print Driver presence
    Check if the file usbprint.sys exists in the system drivers directory (typically C:\Windows\System32\drivers\usbprint.sys). Run 'dir C:\Windows\System32\drivers\usbprint.sys' or use PowerShell: 'Test-Path C:\Windows\System32\drivers\usbprint.sys'.
    Affected if The usbprint.sys driver file exists on the system.
  3. Check for USB printer devices
    Open Device Manager (devmgmt.msc) and look under 'Print queues' or 'Universal Serial Bus controllers' for USB-connected printing devices. Alternatively, run 'Get-PnpDevice -Class Printer -Status OK' in PowerShell to list active printer devices.
    Affected if Any USB-connected printer devices are present and enabled.
  4. Confirm Print Spooler service status
    Run 'services.msc' and locate the Print Spooler service, or run 'sc query spooler' from command line to check if the service is running.
    Affected if The Print Spooler service is running, as the USB Print Driver vulnerability operates through the print subsystem.

You are affected if your Windows version matches one of the specified build ranges AND the USB Print Driver (usbprint.sys) is present with USB printer devices or the Print Spooler service active.

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 the Microsoft security patch for CVE-2026-54111 once released. Until then, limit local access to trusted users only and monitor for suspicious USB device interactions.

Recommended fix Moderate confidence

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

  1. Open Windows Settings and navigate to Windows Update
  2. Check for updates and install all available updates
  3. Verify the installed Windows build version matches or exceeds the fixed version for your product: Windows 11 24h2 should be >= 10.0.26100.8875, Windows 11 25h2 should be >= 10.0.26200.8875, Windows 11 26h1 should be >= 10.0.28000.2525, Windows Server 2025 should be >= 10.0.26100.33158
  4. To check build number: run 'winver' command or go to Settings > System > About
  5. If updates do not bring system to fixed version, check for optional driver updates related to USB printing or contact Microsoft Support for patch KB
Caveat Standard Windows update applies; verify compatibility with existing printing hardware after update

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
  • 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-54111 — 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-54111 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