# CVE-2026-96582: Out-of-bounds Read via Check-after-use in the USBX HID Report Descriptor Parser


- **Severity:** Medium 4.9 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-f2fv-fqrc-h8jr

## What is CVE-2026-96582?

CVE-2026-96582 is a medium-severity vulnerability in Eclipse ThreadX - USBX, published on 20 Oct 2026. 

### Official description

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.

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

## Which versions are affected by CVE-2026-96582?


## How do I fix CVE-2026-96582?

No fix has been published for CVE-2026-96582 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-96582 being exploited?

There is no known exploitation of CVE-2026-96582 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-96582 and fix it if it is affected.

What it is: CVE-2026-96582 is a medium-severity vulnerability in Eclipse ThreadX - USBX, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-96582 in the wild and no public exploit code.

Affected product: Eclipse ThreadX - USBX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-96582/ (Markdown: https://insights.sbomify.com/CVE-2026-96582/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-96582
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-96582
- OSV: https://osv.dev/vulnerability/CVE-2026-96582

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-96582/
Summaries are generated and may contain mistakes; the official description above is the record.