Is CVE-2026-96582 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-96582 being exploited in the wild.

How severe is CVE-2026-96582?

Medium severity, with a CVSS score of 4.9, published 20 October 2026.

Which products and versions are affected?

Eclipse ThreadX USBX <= 6.5.1.202602.

Is there a fix for CVE-2026-96582?

Yes: fixed in USBX 6.5.2.202603. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-96582 attacked?

It is attacked with physical access, in a software library.

Am I affected by CVE-2026-96582?

Check whether you run Eclipse ThreadX USBX at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-96582: USBX HID report descriptor out-of-bounds read

Q: Is there a fix for CVE-2026-96582?

Yes: fixed in USBX 6.5.2.202603. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-96582 attacked?

It is attacked with physical access, in a software library.

Q: Am I affected by CVE-2026-96582?

Check whether you run Eclipse ThreadX USBX at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-96582 · Severity: medium · CVSS 4.9 · Published 2026-10-20

USBX is a USB host/device stack used in embedded systems and IoT devices. A malicious or compromised HID device (keyboard, mouse, etc.) can cause the host to read memory adjacent to its buffers during device enumeration, potentially crashing the system or corrupting internal parser state. Physical access is required to connect the malicious device.

Vendors: Eclipse ThreadX.

Quick answers

Is CVE-2026-96582 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-96582 being exploited in the wild.
How severe is CVE-2026-96582?: Medium severity, with a CVSS score of 4.9, published 20 October 2026.
Which products and versions are affected?: Eclipse ThreadX USBX <= 6.5.1.202602.
Is there a fix for CVE-2026-96582?: Yes: fixed in USBX 6.5.2.202603. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-96582 attacked?: It is attacked with physical access, in a software library.
Am I affected by CVE-2026-96582?: Check whether you run Eclipse ThreadX USBX at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: USBX 6.5.2.202603

Technical details

The HID report descriptor parser validates item lengths after advancing past headers and parsing payloads instead of before, allowing out-of-bounds reads when a peripheral reports a short descriptor. Two code paths are affected: the RTOS _ux_host_class_hid_report_descriptor_get and the standalone enumeration state machine _ux_host_class_hid_report_descriptor_parse. An attacker supplying a specially crafted HID descriptor can trigger reads of uninitialized heap memory, potentially causing a page fault or corrupting parser state.

Affected products

Eclipse ThreadX USBX <= 6.5.1.202602

Timeline

2026-10-02: disclosed
2026-10-20: advisory

References

https://github.com/eclipse-threadx/usbx/security/advisories/GHSA-f2fv-fqrc-h8jr

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.