CVE-2026-47104Public exploit

Application crash via descriptor bounds miscalculation

Published May 27, 2026 · Updated May 27, 2026

Out-of-bounds read in libusb before 1.0.30 allows attackers to crash applications by supplying a malformed USB descriptor. parse_iad_array() compares bLength with the original buffer size rather than the unconsumed length, then reads the next descriptor header one byte beyond the allocation. Exploitation requires control of descriptor data, such as through USB passthrough in a virtualized environment, and interrupts the process that invokes the affected interface-association APIs.

CVSS severity5.1
Medium
EPSS probability0.13%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Out-of-bounds read in libusb before 1.0.30 allows attackers to crash applications by supplying a malformed USB descriptor. parse_iad_array() compares bLength with the original buffer size rather than the unconsumed length, then reads the next descriptor header one byte beyond the allocation. Exploitation requires control of descriptor data, such as through USB passthrough in a virtualized environment, and interrupts the process that invokes the affected interface-association APIs.

The record

CVE
CVE-2026-47104
Published
May 27, 2026
Updated
May 27, 2026
Vendor
libusb
Product
libusb
Classifications
CWE-125, T1499
Attack vector
local
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 27, 2026CVE publishedPublication date reported by the CVE source.
  2. May 27, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <1.0.30

What conditions does exploitation require?

Attack vectorlocal
Required privilegesunauthenticated

What is affected?

libusb · libusbversion=0 <1.0.30

Published CVSS scores

4.0VulnCheckCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
5.1VulnCheckCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
5.5NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-125Out-of-bounds Read
T1499Endpoint Denial of Service

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo