# CVE-2026-96406: VIDEO class descriptor walk consumes device-controlled wTotalLength as its bound


- **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-8qf6-hjvf-g68f

## What is CVE-2026-96406?

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

### Official description

A VideoStreaming interface reports the size of its whole class-specific descriptor block in the `wTotalLength` field of its input header. The USBX host recorded that figure and used it as the budget for walking the format, frame and frame-interval descriptors, without holding it against the configuration descriptor actually received.

A device that reports a `wTotalLength` larger than the descriptors it supplies therefore had its own claim believed. Once the real bytes ran out the walk kept going, dereferencing the cursor past the end of the configuration buffer, in the host's context, whenever the application queried format or frame data.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-96406 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96406 is a medium-severity vulnerability in Eclipse ThreadX -  USBX, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-96406 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-96406/ (Markdown: https://insights.sbomify.com/CVE-2026-96406/index.md)
```

## Sources

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

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