{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-55078 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-55078 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-55078 is a medium-severity vulnerability in Eclipse Foundation ThreadX, published on 14 Oct 2025. 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-2025-55078 and fix it if it is affected.\n\nWhat it is: CVE-2025-55078 is a medium-severity vulnerability in Eclipse Foundation ThreadX, published on 14 Oct 2025. 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-2025-55078 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-2025-55078/ (Markdown: https://insights.sbomify.com/CVE-2025-55078/index.md)","id":"CVE-2025-55078","markdown":"https://insights.sbomify.com/CVE-2025-55078/index.md","name":"CVE-2025-55078","record":{"aliases":["GHSA-wcfg-5jpf-hhxq"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"RTOS kernel","requires_auth":"low_privilege","summary":"An attacker can cause a denial of service in Eclipse ThreadX by providing invalid pointers to system calls that lack proper memory region validation.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"threadx","vendor":"eclipse"}],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-233","name":"Improper Handling of Parameters"}],"description":"In Eclipse ThreadX before version 6.4.3, an attacker can cause a denial of service (crash) by providing a pointer to a reserved or unmapped memory region. Vulnerable system calls had a check of pointers, but that check wasn't verifying whether the pointer is outside the module memory region.","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":"Incomplete validation of kernel object pointers in system calls","id":"CVE-2025-55078","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Missing check for thread priority","id":"CVE-2025-55079"},"packages":[],"prev":{"headline":"Tyler Technologies ERP Pro 9 SaaS application escape","id":"CVE-2025-55077"},"products":["ThreadX"],"published":"2025-10-14","related":[{"cvss_score":7.8,"headline":"Memory corruption in Eclipse ThreadX","id":"CVE-2026-0648","kev_date_added":null,"published":"2026-01-27"},{"cvss_score":7.3,"headline":"Integer overflow in ThreadX","id":"CVE-2024-2212","kev_date_added":null,"published":"2024-03-26"},{"cvss_score":7.2,"headline":"Improper Parameter Check in ThreadX Syscall Implementation","id":"CVE-2025-55080","kev_date_added":null,"published":"2025-10-15"},{"cvss_score":7,"headline":"Missing array size check in _Mtxinit() in the Xtensa port","id":"CVE-2024-2214","kev_date_added":null,"published":"2024-03-26"},{"cvss_score":5.7,"headline":"Missing check for thread priority","id":"CVE-2025-55079","kev_date_added":null,"published":"2025-10-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"2025-10-14","vendors":["Eclipse Foundation"]},"summary":"An attacker can cause a denial of service in Eclipse ThreadX by providing invalid pointers to system calls that lack proper memory region validation.","url":"https://insights.sbomify.com/CVE-2025-55078/"}