Skip to content
Fencer Intel
medium 4.9

CVE-2026-96582 json

Out-of-bounds Read via Check-after-use in the USBX HID Report Descriptor Parser

published last mo. modified 22d ago also EUVD-2026-105000 , GHSA-f2fv-fqrc-h8jr

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository eclipse-threadx/usbx. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
4.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 6%
public exploits
0
none known

Summary

A HID report descriptor is a sequence of items, each declaring in its header how many data bytes follow. The USBX host walks that sequence by advancing over each header and parsing the data behind it.

The walk checked that an item fitted in the descriptor only **after** it had advanced past the header and parsed the payload, and the item analysis it relied on never measured the declared sizes against the bytes actually received. A HID peripheral returning a short report descriptor therefore drove a heap out-of-bounds read during ordinary enumeration.

Patch / fix

  • Eclipse Foundation Eclipse ThreadX - USBX 6.5.2.202603

Is CVE-2026-96582 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
22d ago

Exploit prediction

0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 4.9 CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H

Affected products

  • Eclipse Foundation Eclipse ThreadX - USBX

Classification

Weakness
  • CWE-125 Out-of-bounds Read
  • CWE-1285 Improper Validation of Specified Index, Position, or Offset in Input

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of eclipse-threadx/usbx published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.