{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-91041 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-91041 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-91041 is a high-severity vulnerability in Eclipse ThreadX - FileX, published on 20 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-91041 and fix it if it is affected.\n\nWhat it is: CVE-2026-91041 is a high-severity vulnerability in Eclipse ThreadX - FileX, published on 20 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-91041 in the wild and no public exploit code.\n\nAffected product: Eclipse ThreadX - FileX. 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-91041/ (Markdown: https://insights.sbomify.com/CVE-2026-91041/index.md)","id":"CVE-2026-91041","markdown":"https://insights.sbomify.com/CVE-2026-91041/index.md","name":"CVE-2026-91041","record":{"aliases":["GHSA-c8cj-fj9j-426v"],"analysis":null,"analysis_generated_by":null,"assigner":"eclipse","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-1284","name":"Improper Validation of Specified Quantity in Input"}],"description":"Mounting an attacker-controlled FAT image with fault tolerance enabled causes an out-of-bounds heap write during log replay. The write is attacker-positioned and attacker-valued, and on a common embedded memory layout it reaches the FX_MEDIA driver callback, giving control of the instruction pointer.","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":"FileX fault-tolerant log replay writes past the destination sector when mounting a crafted FAT image","id":"CVE-2026-91041","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"HPACK-indexed cookie fields in Mint HTTP/2 responses bypass max_header_list_size and exhaust client memory","id":"CVE-2026-91043"},"packages":[],"prev":{"headline":"Auth bypass in ash authentication","id":"CVE-2026-91039"},"products":["Eclipse ThreadX - FileX"],"published":"2026-10-20","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-20","vendors":["Eclipse Foundation"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-91041/"}