Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessPhysically connect malicious USB HID device
-
DeliveryDevice returns short HID report descriptor
-
ExploitUSBX enumeration walks descriptor items
-
ExecutionParser reads past received bytes
-
ImpactHeap 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
Affected Packages
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
AV:P/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H
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.
Primary rating from Vendor (eclipse).
CVSS VectorVendor: eclipse
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
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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.
More in Eclipse Threadx Usbx
View allOut-of-bounds heap read in the Eclipse ThreadX USBX host stack can be triggered when a malicious USB device presenting t
An out-of-bounds read exists in the Eclipse ThreadX USBX host stack's USB Video Class handling: when a malicious USB dev
EUVD-2026-105000
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB