{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-55079 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-55079 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-55079 is a medium-severity denial of service vulnerability in Eclipse Foundation ThreadX, published on 15 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-55079 and fix it if it is affected.\n\nWhat it is: CVE-2025-55079 is a medium-severity denial of service vulnerability in Eclipse Foundation ThreadX, published on 15 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-55079 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-55079/ (Markdown: https://insights.sbomify.com/CVE-2025-55079/index.md)","id":"CVE-2025-55079","markdown":"https://insights.sbomify.com/CVE-2025-55079/index.md","name":"CVE-2025-55079","record":{"aliases":["GHSA-w8rw-fqgj-9r49"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Eclipse ThreadX RTOS","requires_auth":"low_privilege","summary":"Attackers can create threads with higher priority than allowed, potentially causing a denial of service in Eclipse ThreadX.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"In Eclipse ThreadX before version 6.4.3, the thread module has a setting of maximum priority. In some cases the check of that maximum priority wasn't performed, allowing, as a result, to obtain a thread with higher priority than expected and causing a possible denial of service.","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":"Missing check for thread priority","id":"CVE-2025-55079","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Improper Parameter Check in ThreadX Syscall Implementation","id":"CVE-2025-55080"},"packages":[],"prev":{"headline":"Incomplete validation of kernel object pointers in system calls","id":"CVE-2025-55078"},"products":["ThreadX"],"published":"2025-10-15","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":"Incomplete validation of kernel object pointers in system calls","id":"CVE-2025-55078","kev_date_added":null,"published":"2025-10-14"}],"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-15","vendors":["Eclipse Foundation"]},"summary":"Attackers can create threads with higher priority than allowed, potentially causing a denial of service in Eclipse ThreadX.","url":"https://insights.sbomify.com/CVE-2025-55079/"}