CVE-2026-58528
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 · uneditedOut-of-bounds read in Windows USB Audio Class driver (usbaudio.sys) allows an unauthorized attacker to disclose information 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 confidenceOut-of-bounds read vulnerability in Windows USB Audio Class driver (usbaudio.sys) allows an attacker with physical access to the machine to read memory beyond allocated buffers, potentially disclosing sensitive information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/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.
-
Locate usbaudio.sys driver fileOpen PowerShell and run: Get-Item 'C:\Windows\System32\drivers\usbaudio.sys' | Select-Object FullName, Version, LengthAffected if The file does not exist on the system (not vulnerable in this case, as the driver is not present)
-
Check usbaudio.sys driver versionRun: driverquery /v | Select-String 'usbaudio' or use PowerShell: Get-WmiObject Win32_PnPSignedDriver | Where-Object {$_.DeviceName -like '*USB Audio*'} | Select-Object DeviceName, DriverVersion, DriverDateAffected if Driver version matches a known vulnerable version from Microsoft's security advisory for this CVE (compare your version to the affected ranges when published)
-
Verify USB Audio Class driver is loadedRun: Get-Process | Where-Object {$_.ProcessName -eq 'audiodg'} - the audiodg.exe process handles audio device I/O including USB audio class driversAffected if The audiodg.exe process is running and USB audio devices have been connected, indicating the vulnerable code path may be active
-
Check for connected USB Audio devicesOpen Device Manager, expand 'Sound, video and game controllers', look for devices with 'USB Audio' in the name; or run: Get-PnpDevice -Class AudioEndpoint | Where-Object {$_.FriendlyName -like '*USB*'}Affected if USB Audio Class devices are present or have been previously connected to the system
The system is affected if usbaudio.sys is present with a version matching the CVE-affected range AND USB audio devices are used or have been connected, allowing a physical attacker to trigger the out-of-bounds read.
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.
From vendor dataApply Microsoft's security update for usbaudio.sys when available; restrict physical access to sensitive systems as an interim control.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58528 — 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-58528 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