Skip to main content

Eclipse ThreadX USBX CVE-2026-96582

| EUVDEUVD-2026-105000 MEDIUM
Out-of-bounds Read (CWE-125)
2026-10-20 eclipse
4.9
CVSS 3.1 · Vendor: eclipse
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Physically connect malicious USB HID device
  2. Delivery
    Device returns short HID report descriptor
  3. Exploit
    USBX enumeration walks descriptor items
  4. Execution
    Parser reads past received bytes
  5. Impact
    Heap out-of-bounds read / crash

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK

1 technique across 1 tactic: Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires the target to run Eclipse ThreadX USBX configured as a USB HOST with the HID class driver active, and requires physical attachment of an attacker-controlled (or malfunctioning) USB HID peripheral that returns a short/truncated HID report descriptor whose item headers declare more data bytes than were actually transferred; the bug fires automatically during normal device enumeration. Exploitation is limited by physical access (AV:P) and the need for a user or attacker to physically connect the device (UI:R); it is not reachable over any network, requires no authentication (PR:N), and does not apply to devices operating only in USB-device/peripheral mode or without the HID class.

Impact

This is a genuinely low-to-moderate, physically-gated issue rather than a remote crisis, and the signals are internally consistent. The CVSS 3.1 vector (AV:P/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H, base 4.9 MEDIUM) requires physical attachment of a malicious USB HID peripheral plus a user action to connect it, which fundamentally caps real-world exposure - there is no network-facing path. Impact is a heap out-of-bounds READ (CWE-125), yielding limited information disclosure (C:L) and primarily a denial of service / crash (A:H); there is no integrity impact (I:N) and no code execution claimed. No EPSS score was supplied, the CVE is NOT on CISA KEV, and no public proof-of-concept is referenced, so exploitation status is 'no public exploit identified at time of analysis.' The only apparent tension is the 'Buffer Overflow' tag versus the actual CWE-125 out-of-bounds READ and the advisory text (a read, not a write/overflow) - treat the issue as an info-leak/DoS, not a memory-corruption RCE. Bottom line: a real but bounded firmware robustness bug whose priority depends entirely on whether the device operates in attacker-reachable USB-host scenarios (kiosks, chargers, field-serviced embedded gear).

Exploit ScenarioDerived

An attacker connects (or convinces a user to connect) a malicious or malfunctioning USB HID device that returns a deliberately truncated/short HID report descriptor to a system running Eclipse ThreadX USBX in host mode. During ordinary enumeration, the descriptor walker advances past an item header and parses declared payload bytes that extend beyond the bytes actually received, causing a heap out-of-bounds read that can leak adjacent heap contents or crash the device. No public exploit code is identified at time of analysis, and physical access plus user interaction are required.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 20, 2026

Heap out-of-bounds read in the Eclipse ThreadX USBX USB host HID class driver is triggered during ordinary device enumeration when a physically attached HID peripheral returns a short or truncated report descriptor whose item headers declare more payload bytes than were actually transferred. The flaw affects USBX builds configured as a USB host with HID support, requires physical access and a user action to connect the device, and needs no authentication (CVSS 3.1: 4.9, AV:P/AC:L/PR:N/UI:R), with the main impact being a crash or denial of service plus limited information disclosure. No public exploit code or confirmed active exploitation was identified at the time of analysis.

RemediationAI

Apply the fix referenced in the Eclipse ThreadX USBX security advisory GHSA-f2fv-fqrc-h8jr; no exact fixed version number was provided in the available data, so confirm the patched release with the vendor before deployment. Where an immediate update is not possible, disable the USBX host HID class driver in the build configuration if HID peripherals are not required (trade-off: no keyboard, mouse, or other HID device support), and physically restrict access to exposed USB host ports using port blockers, sealed enclosures, or epoxy-filled connectors to prevent untrusted peripherals from being attached (trade-off: operational inconvenience and reduced field serviceability). If HID support is mandatory, insert a descriptor-sanitizing USB firewall or proxy between the host and untrusted devices, or gate enumeration to an allowlist of known VID/PID pairs (trade-off: added BOM/latency, and an allowlisted but malicious device can still trigger the parser). Enabling heap bounds checking or an MPU guard region around descriptor buffers can convert the out-of-bounds read into a controlled fault (trade-off: performance and memory overhead).

Affected VersionsENISA

Eclipse ThreadX - USBX 0 ≤6.5.1.202602

Affected Packages

euvd eclipse_threadx_usbx no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Eclipse ThreadX USBX is an embedded USB host/device stack. Its HID class driver parses the HID report descriptor, a sequence of items whose 1-byte prefix encodes tag, type, and a size field indicating how many data bytes follow. The parser advances past each header and parses the declared payload before validating that the whole item fits within the received descriptor, and the subsequent item analysis never compares declared sizes against the bytes actually transferred. A malicious or malfunctioning HID peripheral can therefore return a short descriptor that terminates mid-item, causing the walk to read past the end of the heap buffer holding the descriptor (CWE-125). The result is an out-of-bounds read during enumeration that can disclose adjacent heap memory (C:L) and more reliably crash the host stack (A:H). This is a descriptor-length validation defect rather than a write overflow, despite the 'Buffer Overflow' tagging in intelligence feeds.

Know when Eclipse Threadx Usbx gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (eclipse) PRIMARY 4.9 MEDIUM
AV:P/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H
vuln.today AI 4.9 MEDIUM

Physical USB attachment drives AV:P and UI:R, no auth needed (PR:N); out-of-bounds read yields limited info leak (C:L) and a crash (A:H), with no integrity impact.

3.1 AV:P/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H
4.0 AV:P/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (eclipse).

CVSS VectorVendor: eclipse

Attack Vector
Physical
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Medium
widely-used embedded RTOS USB stack, but only USBX-host HID deployments affected
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

24
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +24
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy