CVE-2026-47104

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 27, 2026

Last Modified

July 14, 2026

Advisory Details (5)

Auto-updated Jun 16, 2026
Patch available. Sources: github_commit, github_pr, github_release.
generic

libusb < 1.0.30 Out-of-Bounds Read in parse_iad_array() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/libusb-out-of-bounds-read-in-parse-iad-array
github_release Patch Available

v1.0.30: libusb 1.0.30

Patch available: libusb/libusb v1.0.30

https://github.com/libusb/libusb/releases/tag/v1.0.30
github_pr

Fix/descriptor parser memory safety

Upstream fix in progress (PR #1814 · libusb/libusb, state=closed)

https://github.com/libusb/libusb/pull/1814
generic

Two memory-safety bugs in libusb/descriptor.c found by fuzzing (parse_interface NULL endpoint, parse_iad_array OOB read) · Issue #1813 · libusb/libusb · GitHub

https://github.com/libusb/libusb/issues/1813
github_commit Patch Available

commit 578ab76b4c43 (libusb/libusb)

Patch available: libusb/libusb v1.0.30-rc2 (contains commit 578ab76b4c43)

https://github.com/libusb/libusb/commit/578ab76b4c434f8b204137ab6d7310689c7a9704

Vendor Advisories for CVE-2026-47104(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatlibusb1-main-1.0.30-1.hum12026-05-21redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libusb-1.02:1.0.24-3 ... 2:1.0.30~rc2-1 (20 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libusb-1.02:1.0.26-1 ... 2:1.0.30~rc2-1 (16 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libusb-1.02:1.0.28-1 ... 2:1.0.30~rc2-1 (6 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libusb-1.02:1.0.28-1, 2:1.0.29-1, 2:1.0.29-2, 2:1.0.30~rc1-1, 2:1.0.30~rc2-12:1.0.30-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 66× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 197 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 05:16 UTCEG score recompute
  11. 2026-08-25 05:16 UTCVendor advisory
  12. 2026-08-25 05:16 UTCGHSA enrichment
  13. 2026-08-23 15:00 UTCEG score recompute
  14. 2026-08-23 15:00 UTCVendor advisory
  15. 2026-08-23 15:00 UTCGHSA enrichment
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-21 23:49 UTCEPSS rescore
  18. 2026-08-21 20:35 UTCEG score recompute
  19. 2026-08-21 20:35 UTCVendor advisory
  20. 2026-08-21 20:35 UTCGHSA enrichment
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-20 11:18 UTCEG score recompute
  23. 2026-08-20 11:18 UTCVendor advisory
  24. 2026-08-20 11:18 UTCGHSA enrichment
  25. 2026-08-19 17:04 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-17 09:16 UTCEG score recompute
  4. 2026-08-17 09:16 UTCVendor advisory
  5. 2026-08-17 09:16 UTCGHSA enrichment
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 05:42 UTCEG score recompute
  8. 2026-08-16 05:42 UTCVendor advisory
  9. 2026-08-16 05:42 UTCGHSA enrichment
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 03:35 UTCEG score recompute
  12. 2026-08-15 03:35 UTCVendor advisory
  13. 2026-08-15 03:35 UTCGHSA enrichment
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-14 01:27 UTCEG score recompute
  16. 2026-08-14 01:27 UTCVendor advisory
  17. 2026-08-14 01:27 UTCGHSA enrichment
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-12 13:51 UTCEPSS rescore
  20. 2026-08-12 11:29 UTCEG score recompute
  21. 2026-08-12 11:29 UTCVendor advisory
  22. 2026-08-12 11:29 UTCGHSA enrichment
  23. 2026-08-11 08:55 UTCEG score recompute
  24. 2026-08-11 08:55 UTCVendor advisory
  25. 2026-08-11 08:55 UTCGHSA enrichment
  26. 2026-08-11 00:00 UTCEPSS rescore
  27. 2026-08-10 06:47 UTCEG score recompute
  28. 2026-08-10 06:47 UTCVendor advisory
  29. 2026-08-10 06:47 UTCGHSA enrichment
  30. 2026-08-09 13:46 UTCEPSS rescore
  31. 2026-08-09 04:40 UTCEG score recompute
  32. 2026-08-09 04:40 UTCVendor advisory
  33. 2026-08-09 04:40 UTCGHSA enrichment
  34. 2026-08-08 16:37 UTCEPSS rescore
  35. 2026-08-08 02:33 UTCEG score recompute
  36. 2026-08-08 02:33 UTCVendor advisory
  37. 2026-08-08 02:33 UTCGHSA enrichment
  38. 2026-08-07 00:26 UTCEG score recompute
  39. 2026-08-07 00:26 UTCVendor advisory
  40. 2026-08-07 00:26 UTCGHSA enrichment
  41. 2026-08-06 13:47 UTCEPSS rescore
  42. 2026-08-05 20:52 UTCEG score recompute
  43. 2026-08-05 20:52 UTCVendor advisory
  44. 2026-08-05 20:52 UTCGHSA enrichment
  45. 2026-08-05 19:17 UTCEPSS rescore
  46. 2026-08-04 15:10 UTCEPSS rescore
  47. 2026-08-04 10:39 UTCEPSS rescore
  48. 2026-08-03 19:30 UTCEG score recompute
  49. 2026-08-03 19:30 UTCVendor advisory
  50. 2026-08-03 19:30 UTCGHSA enrichment
  51. 2026-08-03 10:36 UTCEPSS rescore
  52. 2026-08-02 17:23 UTCEG score recompute
  53. 2026-08-02 17:23 UTCVendor advisory
  54. 2026-08-02 17:23 UTCGHSA enrichment
  55. 2026-08-02 02:27 UTCEPSS rescore
  56. 2026-08-01 15:15 UTCEG score recompute
  57. 2026-08-01 15:15 UTCVendor advisory
  58. 2026-08-01 15:15 UTCGHSA enrichment
  59. 2026-08-01 04:16 UTCEPSS rescore
  60. 2026-07-31 07:30 UTCEG score recompute
  61. 2026-07-31 07:30 UTCVendor advisory
  62. 2026-07-31 07:30 UTCGHSA enrichment
  63. 2026-07-30 16:28 UTCEPSS rescore
  64. 2026-07-30 01:30 UTCEPSS rescore
  65. 2026-07-29 15:08 UTCEG score recompute
  66. 2026-07-29 15:08 UTCVendor advisory
  67. 2026-07-29 15:08 UTCGHSA enrichment
  68. 2026-07-28 15:37 UTCEPSS rescore
  69. 2026-07-27 14:13 UTCEPSS rescore
  70. 2026-07-27 10:19 UTCEG score recompute
  71. 2026-07-27 10:19 UTCVendor advisory
  72. 2026-07-27 10:19 UTCGHSA enrichment
  73. 2026-07-26 14:54 UTCEPSS rescore
  74. 2026-07-26 14:54 UTCEPSS rescore
  75. 2026-07-25 14:18 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-47104?
CVE-2026-47104 is a medium vulnerability published on May 27, 2026. libusb before version 1.0.30 contains a one-byte out-of-bounds read vulnerability in parseiadarray() 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…
When was CVE-2026-47104 disclosed?
CVE-2026-47104 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47104 actively exploited?
CVE-2026-47104 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.1% of all scored CVEs.
What is the CVSS score of CVE-2026-47104?
CVE-2026-47104 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-47104?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47104, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47104

Explore →

Is Your Infrastructure Affected by CVE-2026-47104?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs