# CVE-2026-95107: Module object allocation size overflow corrupts the manager object pool


- **Severity:** High 7.0 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-63qc-jcr6-qw6r

## What is CVE-2026-95107?

CVE-2026-95107 is a high-severity vulnerability in Eclipse ThreadX, published on 20 Oct 2026. 

### Official 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.

Weakness: CWE-787 (Out-of-bounds Write), CWE-680 (Integer Overflow to Buffer Overflow), CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2026-95107?


## How do I fix CVE-2026-95107?

No fix has been published for CVE-2026-95107 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-95107 being exploited?

There is no known exploitation of CVE-2026-95107 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-95107 and fix it if it is affected.

What it is: CVE-2026-95107 is a high-severity vulnerability in Eclipse ThreadX, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-95107 in the wild and no public exploit code.

Affected product: Eclipse ThreadX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-95107/ (Markdown: https://insights.sbomify.com/CVE-2026-95107/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-95107
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-95107
- OSV: https://osv.dev/vulnerability/CVE-2026-95107

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-95107/
Summaries are generated and may contain mistakes; the official description above is the record.