{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-95107 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-95107 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-95107 is a high-severity vulnerability in Eclipse ThreadX, published on 20 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-95107 and fix it if it is affected.\n\nWhat it is: CVE-2026-95107 is a high-severity vulnerability in Eclipse ThreadX, published on 20 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-95107 in the wild and no public exploit code.\n\nAffected product: Eclipse 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-95107/ (Markdown: https://insights.sbomify.com/CVE-2026-95107/index.md)","id":"CVE-2026-95107","markdown":"https://insights.sbomify.com/CVE-2026-95107/index.md","name":"CVE-2026-95107","record":{"aliases":["GHSA-63qc-jcr6-qw6r"],"analysis":null,"analysis_generated_by":null,"assigner":"eclipse","cpe":[],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-680","name":"Integer Overflow to Buffer Overflow"},{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"A ThreadX module chooses `object_size` when it calls `txm_module_object_allocate`. The Module Manager adds its own 16-byte private header to that size and asked the object pool for the result **without checking the addition**. A size near the top of a `ULONG` wrapped, the pool served a block far smaller than the header, and the manager then wrote the header past the end of it and into the neighbouring byte-pool block.","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":"Module object allocation size overflow corrupts the manager object pool","id":"CVE-2026-95107","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Deleting a user-mode module thread leaks its privileged kernel stack","id":"CVE-2026-95108"},"packages":[],"prev":{"headline":"Gitea review and execution mismatch through duplicate tree entries","id":"CVE-2026-95106"},"products":["Eclipse ThreadX"],"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":"partial"},"state":"PUBLISHED","updated":"2026-10-20","vendors":["Eclipse Foundation"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-95107/"}