CVE-2026-47104 Vulnerability Analysis & Exploit Details

CVE-2026-47104
Vulnerability Scoring

4.0
/10
Moderate Risk

Exploiting CVE-2026-47104 requires specific conditions, leading to a moderate security impact.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-47104 Details

Status: Analyzed

Last updated: 🕙 14 Jul 2026, 22:16 UTC
Originally published on: 🕑 27 May 2026, 14:17 UTC

Time between publication and last update: 48 days

CVSS Release: version 3

CVSS3 Source

disclosure@vulncheck.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

CVE-2026-47104 Vulnerability Summary

CVE-2026-47104: 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.

Assessing the Risk of CVE-2026-47104

Access Complexity Graph

The exploitability of CVE-2026-47104 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-47104

With low attack complexity and no required privileges, CVE-2026-47104 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-47104, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-47104, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2026-47104 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2026-47104 poses no threat to data integrity.
  • Availability: Low
    CVE-2026-47104 may slightly degrade system performance without fully affecting service availability.

CVE-2026-47104 References

External References

CWE Common Weakness Enumeration

CWE-125

CAPEC Common Attack Pattern Enumeration and Classification

  • Overread Buffers CAPEC-540 An adversary attacks a target by providing input that causes an application to read beyond the boundary of a defined buffer. This typically occurs when a value influencing where to start or stop reading is set to reflect positions outside of the valid memory location of the buffer. This type of attack may result in exposure of sensitive information, a system crash, or arbitrary code execution.

Vulnerable Configurations

  • cpe:2.3:a:libusb:libusb:0.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:0.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:0.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:0.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:0.9.2:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:0.9.2:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:0.9.3:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:0.9.3:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:0.9.4:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:0.9.4:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.7:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.7:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.8:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.8:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.9:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.9:rc3:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.9:rc3:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.9:rc4:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.9:rc4:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.9:rc5:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.9:rc5:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.10:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.10:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.10:rc1:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.10:rc1:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.11:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.11:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.11:rc1:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.11:rc1:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.12:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.12:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.12:rc1:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.12:rc1:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.13:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.13:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.13:rc1:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.13:rc1:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.13:rc2:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.13:rc2:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.14:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.14:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.15:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.15:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.15:rc1:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.15:rc1:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.15:rc2:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.15:rc2:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.15:rc3:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.15:rc3:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.16:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.16:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.16:rc1:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.16:rc1:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.16:rc2:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.16:rc2:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.16:rc3:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.16:rc3:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.17:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.17:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.17:rc1:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.17:rc1:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.18:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.18:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.18:rc1:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.18:rc1:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.19:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.19:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.19:rc1:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.19:rc1:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.19:rc2:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.19:rc2:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.20:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.20:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.20:rc1:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.20:rc1:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.20:rc2:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.20:rc2:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.20:rc3:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.20:rc3:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.21:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.21:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.21:rc1:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.21:rc1:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.21:rc2:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.21:rc2:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.21:rc3:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.21:rc3:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.21:rc4:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.21:rc4:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.21:rc5:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.21:rc5:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.21:rc6:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.21:rc6:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.22:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.22:*:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.22:rc1:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.22:rc1:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.22:rc2:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.22:rc2:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.22:rc3:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.22:rc3:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.22:rc4:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.22:rc4:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.23:-:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.23:-:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.23:rc1:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.23:rc1:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.23:rc2:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.23:rc2:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.23:rc3:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.23:rc3:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.24:-:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.24:-:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.24:rc1:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.24:rc1:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.25:-:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.25:-:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.25:rc1:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.25:rc1:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.26:-:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.26:-:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.26:rc1:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.26:rc1:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.27:-:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.27:-:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.27:rc1:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.27:rc1:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.27:rc2:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.27:rc2:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.28:-:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.28:-:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.28:rc1:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.28:rc1:*:*:*:*:*:*
  • cpe:2.3:a:libusb:libusb:1.0.29:*:*:*:*:*:*:*
    cpe:2.3:a:libusb:libusb:1.0.29:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-47104: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-108968 – A weakness has been identified in SourceCodester Performance Indicator System 1.0. The affected element is an unknown function of the file /opils/s...
  • CVE-2026-108967 – A security flaw has been discovered in SourceCodester Performance Indicator System 1.0. Impacted is an unknown function of the file /opils/staff/ed...
  • CVE-2026-108966 – A vulnerability was identified in SourceCodester Performance Indicator System 1.0. This issue affects some unknown processing of the file /opils/st...
  • CVE-2026-109758 – Perforce Helix Authentication Service (HAS) deployments that retain the shipped default SCIM bearer token are vulnerable to unauthorized access whe...
  • CVE-2026-108965 – A vulnerability was determined in SourceCodester Performance Indicator System 1.0. This vulnerability affects unknown code of the file /opils/staff...