{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-102757 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-102757 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102757 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-102757 and fix it if it is affected.\n\nWhat it is: CVE-2026-102757 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-102757 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-102757/ (Markdown: https://insights.sbomify.com/CVE-2026-102757/index.md)","id":"CVE-2026-102757","markdown":"https://insights.sbomify.com/CVE-2026-102757/index.md","name":"CVE-2026-102757","record":{"aliases":["GHSA-j3fp-8rcq-xfj5","GHSA-rrjj-jwcw-hvf8"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ThreadX RTOS","requires_auth":"low_privilege","summary":"An unprivileged ThreadX module can bypass memory protection to execute privileged memory operations, allowing privilege escalation and potential code execution.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-843","name":"Access of Resource Using Incompatible Type"},{"id":"CWE-823","name":"Use of Out-of-range Pointer Offset"},{"id":"CWE-822","name":"Untrusted Pointer Dereference"},{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"An unprivileged, memory-protected ThreadX module can have the kernel read and write memory at addresses of its choosing, in privileged mode, and can use that to clear the MPU enable bit and remove its own isolation boundary.\n\nThe Module Manager decided whether a privileged service could dereference an object address a module named by asking only whether that address fell outside the module. The manager's object pool is outside every module, so the test was satisfied by an address shifted into the interior of one of the module's own privileged allocations, which denotes no object at all. The bytes such an address presents as a control block are bytes the module put there through ordinary create and set services, so the control block ID at the front of them could be made to read as any type the module chose, and the `_txe_` layer's ID test then agreed. The reported chain uses that to reach a privileged `memset` across an attacker-chosen range.","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":"Privilege escalation in ThreadX","id":"CVE-2026-102757","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in NetX Duo","id":"CVE-2026-102758"},"packages":[],"prev":{"headline":"DataEase bar-horizontal Axis Label Tooltip Stored Cross-Site Scripting","id":"CVE-2026-102756"},"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-10-02","vendors":["Eclipse Foundation"]},"summary":"An unprivileged ThreadX module can bypass memory protection to execute privileged memory operations, allowing privilege escalation and potential code execution.","url":"https://insights.sbomify.com/CVE-2026-102757/"}