# CVE-2026-94202: Module block-pool create validates two of the four parameter words it reads


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:L/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-5w57-xhwq-v7wq

## What is CVE-2026-94202?

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

### Official description

The Module Manager's block-pool create dispatcher proved that two `ALIGN_TYPE` words of the extra-parameter array a memory-protected module supplies lay inside the module's data, and then used indices 0 through 3 of that array.

One of the two unproved words is read by the dispatcher's own buffer check, which takes index 1 as the pool start and index 2 as the length to range-check it over. So the out-of-bounds read is performed by the validation code itself, before the kernel service is reached, and the size the caller's pool start is then validated against is a word the manager has not proved the module owns. The other unproved word is read when the service's argument list is built.

Vulnerable function: `_txm_module_manager_tx_block_pool_create_dispatch`, in `common_modules/module_manager/inc/txm_module_manager_dispatch.h`.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-94202 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94202 is a medium-severity vulnerability in Eclipse ThreadX, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-94202 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-94202/ (Markdown: https://insights.sbomify.com/CVE-2026-94202/index.md)
```

## Sources

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

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