{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-102711 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-102711 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102711 is a medium-severity memory corruption vulnerability in `eclipse-threadx/threadx` (module manager / loadable-module loader), published on 29 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-102711 and fix it if it is affected.\n\nWhat it is: CVE-2026-102711 is a medium-severity memory corruption vulnerability in `eclipse-threadx/threadx` (module manager / loadable-module loader), published on 29 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-102711 in the wild and no public exploit code.\n\nAffected product: `eclipse-threadx/threadx` (module manager / loadable-module loader). 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-102711/ (Markdown: https://insights.sbomify.com/CVE-2026-102711/index.md)","id":"CVE-2026-102711","markdown":"https://insights.sbomify.com/CVE-2026-102711/index.md","name":"CVE-2026-102711","record":{"aliases":["GHSA-w4rq-vh43-v5q5"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ThreadX RTOS","requires_auth":"none","summary":"Attacker-controlled module loading in ThreadX RTOS allows heap out-of-bounds reads and bypasses integrity checks, potentially leading to code execution or denial of service.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[],"cvss":{"score":5.6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:A/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"},{"id":"CWE-1284","name":"Improper Validation of Specified Quantity in Input"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"Two issues in the ThreadX loadable-module loader, reached when a device loads an attacker-controlled module object via `_txm_module_manager_memory_load` / `_txm_module_manager_in_place_load` — APIs that take ONLY a base pointer, no image length, so every size/offset field in `TXM_MODULE_PREAMBLE` is fully attacker-trusted: (1) a heap OOB **read** (`code_size` trusted as the source-image length in the code-copy loop), and (2) a control-flow-integrity / defense-in-depth gap (module entry/start/callback/stop pointers computed as `code_start + preamble_offset` with only a `!= 0` check, and the preamble `checksum` never verified). No controlled OOB write was found (honest — the copy destination is overflow-guarded).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in `eclipse-threadx/threadx` (module manager / loadable-module loader)","id":"CVE-2026-102711","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in NetX Duo","id":"CVE-2026-102712"},"packages":[],"prev":{"headline":"Privilege escalation in eclipse-threadx/threadx","id":"CVE-2026-102710"},"products":["`eclipse-threadx/threadx` (module manager / loadable-module loader)"],"published":"2026-09-29","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-09-29","vendors":["Eclipse Foundation"]},"summary":"Attacker-controlled module loading in ThreadX RTOS allows heap out-of-bounds reads and bypasses integrity checks, potentially leading to code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2026-102711/"}