CVE-2026-47104

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.2% (8th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.0 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-05-27) is not newer than that change (2026-10-14), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

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.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 27, 2026

Last Modified

October 14, 2026

Advisory Details (5)

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

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 pull request

Fix/descriptor parser memory safety

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

https://github.com/libusb/libusb/pull/1814
Web page

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 / EcosystemFix (by version range) / 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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libusb-1.02:1.0.24-3 ... 2:1.0.30~rc2-1 (20 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libusb-1.02:1.0.26-1 ... 2:1.0.30~rc2-1 (16 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libusb-1.02:1.0.28-1 ... 2:1.0.30~rc2-1 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
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-1
  • every version up to 2:1.0.30-1: fixed in 2:1.0.30-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
libusb1.0.22b2 ... 1.0.30rc2 (31 versions)
  • every version up to 1.0.30: fixed in 1.0.30
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 34× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 246 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 146 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Same product

1 shown

Debian:11:libusb-1.0

Same vendor

1 shown

redhat:RHSA-2026:20075

Frequently asked(5)

What is CVE-2026-47104?
CVE-2026-47104 is a medium-severity vulnerability; its CVE record was 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 made public?
CVE-2026-47104 was made public on April 25, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on May 27, 2026. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2026-47104 actively exploited?
CVE-2026-47104 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-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?
A fix for CVE-2026-47104 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47104 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs