LiveActive security incident?Get immediate response
CVE Record

CVE-2026-47104: libusb < 1.0.30 Out-of-Bounds Read in parse_iad_array()

libusb before version 1.0.30 contains a one-byte out-of-bounds read vulnerability in parse_iad_array() in descriptor.c that allows attackers to trigger a denial of service by supplying a malformed USB descriptor whose bLength equals size minus one, causing the bounds check to use the original buffer size instead of the remaining size. Attackers in virtualized environments with USB passthrough can supply crafted descriptors through libusb_get_active_interface_association_descriptors or libusb_get_interface_association_descriptors to read one byte past the end of the malloc allocation, resulting in a denial of service.

MediumCVSS 5.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-47104 is a libusb memory-read bug fixed in 1.0.30. A malformed USB descriptor can make affected software read one byte past an allocated buffer and crash or fail, creating denial-of-service risk. The main concern is systems or applications that process USB devices, especially with USB passthrough in virtualized environments.

Executive priority

Treat this as a moderate availability issue, not an emergency breach indicator. Prioritize patching on virtualization hosts, endpoint tools, hardware-management software, and products that parse USB devices. Business urgency rises where crashes could interrupt operations or tenant isolation assumptions depend on USB passthrough controls.

Technical view

libusb before 1.0.30 has a CWE-125 out-of-bounds read in parse_iad_array() in descriptor.c. The described flaw involves a malformed descriptor length edge case where validation uses the original buffer size instead of remaining buffer size. The recorded CVSS 4.0 score is 5.1 with local attack vector and low availability impact.

Likely exposure

Exposure is most likely where libusb is installed directly, bundled into applications, or statically linked into software that enumerates USB descriptors. Virtualized environments allowing USB passthrough are specifically noted. Internet-facing exposure is not indicated by the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The described attacker position is local or virtualized USB access without privileges or user interaction. Public issue, pull request, advisory, and patch references exist, so defenders should assume technical details are available.

Researcher notes

The available evidence supports a one-byte out-of-bounds read with denial-of-service impact. The patch, issue, and pull request should be reviewed for exact code-level behavior. Do not expand scope beyond libusb before 1.0.30 unless downstream vendors confirm affected bundled copies.

Mitigation direction

  • Upgrade libusb to version 1.0.30 or a vendor-provided fixed build.
  • Inventory applications and appliances that bundle or statically link libusb.
  • Restrict USB passthrough to trusted users and guests where feasible.
  • Track operating system and package vendor advisories for fixed downstream builds.
  • Restart or redeploy affected applications after updating the library.

Validation and detection

  • Confirm installed libusb versions are 1.0.30 or vendor-fixed builds.
  • Review SBOMs and dependency manifests for libusb before 1.0.30.
  • Check virtualization settings for unnecessary USB passthrough exposure.
  • Verify affected applications still handle normal USB descriptor parsing after updates.
  • Attach remediation evidence to vulnerability-management tickets.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-125: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-47104 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.1 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
1ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.1CVSS 4.0MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NVulnCheck
4CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L2.51.4VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

5.1Medium
CVSS 4.0 vector shape for CVE-2026-47104Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
libusblibusb0affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.