{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-96582 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-96582 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-96582 is a medium-severity vulnerability in Eclipse ThreadX - USBX, published on 20 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-96582 and fix it if it is affected.\n\nWhat it is: CVE-2026-96582 is a medium-severity vulnerability in Eclipse ThreadX - USBX, published on 20 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-96582 in the wild and no public exploit code.\n\nAffected product: Eclipse ThreadX - USBX. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-96582/ (Markdown: https://insights.sbomify.com/CVE-2026-96582/index.md)","id":"CVE-2026-96582","markdown":"https://insights.sbomify.com/CVE-2026-96582/index.md","name":"CVE-2026-96582","record":{"aliases":["GHSA-f2fv-fqrc-h8jr"],"analysis":null,"analysis_generated_by":null,"assigner":"eclipse","cpe":[],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-1285","name":"Improper Validation of Specified Index, Position, or Offset in Input"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"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.\n\nThe 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Out-of-bounds Read via Check-after-use in the USBX HID Report Descriptor Parser","id":"CVE-2026-96582","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Use of Hard-coded Credentials in Viidure Dashcam Android Application","id":"CVE-2026-96587"},"packages":[],"prev":{"headline":"Authorization Bypass Through User-Controlled Key vulnerability in ash-project ash allows a user of one tenant to read, overwrite and take ov","id":"CVE-2026-96581"},"products":["Eclipse ThreadX - USBX"],"published":"2026-10-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-20","vendors":["Eclipse Foundation"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-96582/"}