CVE-2026-58543
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 · uneditedConcurrent execution using shared resource with improper synchronization ('race condition') in Windows USB Print Driver allows an authorized attacker to elevate privileges with a physical attack.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
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 confidenceA race condition vulnerability exists in the Windows USB Print Driver where concurrent execution shares a resource without proper synchronization. An attacker with physical access to the system can exploit this timing vulnerability to elevate privileges from their current authorized access level to higher system privileges.
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< 10.0.26100.8875< 10.0.26200.8875< 10.0.28000.2269< 10.0.26100.33158CVSS 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
- Physical
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows version against affected buildsRun 'winver' or 'systeminfo' and note the Windows build number displayed. Compare this to the affected version ranges: Windows 11 24h2 (below 10.0.26100.8875), Windows 11 25h2 (below 10.0.26200.8875), Windows 11 26h1 (below 10.0.28000.2269), Windows Server 2025 (below 10.0.26100.33158).Affected if Your Windows build number falls within any of the affected version ranges listed.
-
Verify USB Print Driver is presentOpen Device Manager, expand 'Print queues' or 'Universal Serial Bus controllers', look for USB Printing Support or USB Print Driver entries. Alternatively, check for usbprint.sys in C:\Windows\System32\drivers\.Affected if The USB Print Driver component is installed on your system.
-
Confirm USB printing capability is enabledOpen Services (services.msc) and check if the 'Print Spooler' service is running, or check Windows Features for 'USB Printing Support' under optional Windows features.Affected if The Print Spooler service or USB printing features are enabled on the system.
Your system is affected if it runs a Windows version within the affected build ranges AND has the USB Print Driver functionality present and enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.26100.887510.0.26100.3315810.0.26200.8875
Apply Microsoft's security updates for the Windows USB Print Driver when available. Until then, limit physical access to affected systems and monitor for suspicious USB device interactions.
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.2269 or later / Windows Server 2025 build 10.0.26100.33158 or later
- Open Windows Settings
- Navigate to Windows Update
- Check for updates and install all available updates
- Verify the installed build version matches or exceeds: Windows 11 24h2: 10.0.26100.8875 | Windows 11 25h2: 10.0.26200.8875 | Windows 11 26h1: 10.0.28000.2269 | Windows Server 2025: 10.0.26100.33158
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-58543 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-58543 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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