{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-102709 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-102709 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102709 is a high-severity vulnerability in Eclipse Foundation ThreadX, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-102709 and fix it if it is affected.\n\nWhat it is: CVE-2026-102709 is a high-severity vulnerability in Eclipse Foundation ThreadX, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-102709 in the wild and no public exploit code.\n\nAffected product: Eclipse Foundation ThreadX. 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-102709/ (Markdown: https://insights.sbomify.com/CVE-2026-102709/index.md)","id":"CVE-2026-102709","markdown":"https://insights.sbomify.com/CVE-2026-102709/index.md","name":"CVE-2026-102709","record":{"aliases":["GHSA-75rq-fmfg-xmgx","GHSA-ffg5-m7vh-vwrp"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ThreadX RTOS","requires_auth":"low_privilege","summary":"Attackers in the non-secure world can read secure memory via improper pointer validation in ThreadX TrustZone-M functions, potentially exposing cryptographic keys.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-822","name":"Untrusted Pointer Dereference"},{"id":"CWE-501","name":"Trust Boundary Violation"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Improper validation of non-secure (NS) pointers in multiple TrustZone-M non-secure callable (NSC) entry functions allows an attacker executing in the non-secure world to supply pointers to secure memory. The secure firmware subsequently dereferences these attacker-controlled pointers without verifying that they reference non-secure memory, resulting in unintended disclosure of secure memory contents. This violates the isolation guarantees provided by Arm TrustZone-M and can be leveraged as a memory disclosure or corruption primitive that may enable recovery of sensitive cryptographic material.","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":"Information disclosure in ThreadX","id":"CVE-2026-102709","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in eclipse-threadx/threadx","id":"CVE-2026-102710"},"packages":[],"prev":{"headline":"Arm: multiple issues with GNTTABOP_cache_flush","id":"CVE-2026-102702"},"products":["ThreadX"],"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":"total"},"state":"PUBLISHED","updated":"2026-09-30","vendors":["Eclipse Foundation"]},"summary":"Attackers in the non-secure world can read secure memory via improper pointer validation in ThreadX TrustZone-M functions, potentially exposing cryptographic keys.","url":"https://insights.sbomify.com/CVE-2026-102709/"}