CVE-2026-23679

MEDIUMNVD 5.56.2▲
EchelonGraph scoreMEDIUM confidence

Score 6.2 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 5.5; sources differ by 0.7.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
6.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

libusb before version 1.0.30 contains a NULL pointer dereference vulnerability that allows attackers to crash applications by supplying a malformed USB configuration descriptor where an interface claims bNumEndpoints greater than zero but is followed by a class-specific descriptor whose bLength exceeds the remaining buffer size, causing parse_interface() to return early without allocating the endpoint array. Attackers can exploit this flaw through libusb_get_active_config_descriptor or libusb_get_config_descriptor by providing crafted descriptors via virtualized USB passthrough, file-based descriptor parsing, or network sources, causing any application iterating over endpoints to dereference a NULL endpoint pointer and crash.

CVSS v3
5.5
EG Score
6.2(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity62% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

May 27, 2026

Last Modified

July 14, 2026

Advisory Details (5)

Auto-updated Jun 13, 2026
Patch available. Sources: github_commit, github_pr, github_release.
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
generic

libusb < 1.0.30 NULL Pointer Dereference in parse_interface() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/libusb-null-pointer-dereference-in-parse-interface
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
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-23679(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 6× in last 7d / 68× 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 226 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-23679?
CVE-2026-23679 is a medium vulnerability published on May 27, 2026. libusb before version 1.0.30 contains a NULL pointer dereference vulnerability that allows attackers to crash applications by supplying a malformed USB configuration descriptor where an interface claims bNumEndpoints greater than zero but is followed by a class-specific descriptor whose bLength…
When was CVE-2026-23679 disclosed?
CVE-2026-23679 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-23679 actively exploited?
CVE-2026-23679 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 91.9% of all scored CVEs.
What is the CVSS score of CVE-2026-23679?
CVE-2026-23679 has a CVSS v3 base score of 5.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 6.2.
How do I remediate CVE-2026-23679?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23679, 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-23679

Explore →

Is Your Infrastructure Affected by CVE-2026-23679?

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

Start Free Scan →Browse All CVEs