# CVE-2026-102711: Memory corruption in `eclipse-threadx/threadx` (module manager / loadable-module loader)

> Attacker-controlled module loading in ThreadX RTOS allows heap out-of-bounds reads and bypasses integrity checks, potentially leading to code execution or denial of service.

- **Severity:** Medium 5.6 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:A/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-w4rq-vh43-v5q5

## What is CVE-2026-102711?

CVE-2026-102711 is a medium-severity memory corruption vulnerability in `eclipse-threadx/threadx` (module manager / loadable-module loader), published on 29 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Two issues in the ThreadX loadable-module loader, reached when a device loads an attacker-controlled module object via `_txm_module_manager_memory_load` / `_txm_module_manager_in_place_load` — APIs that take ONLY a base pointer, no image length, so every size/offset field in `TXM_MODULE_PREAMBLE` is fully attacker-trusted: (1) a heap OOB **read** (`code_size` trusted as the source-image length in the code-copy loop), and (2) a control-flow-integrity / defense-in-depth gap (module entry/start/callback/stop pointers computed as `code_start + preamble_offset` with only a `!= 0` check, and the preamble `checksum` never verified). No controlled OOB write was found (honest — the copy destination is overflow-guarded).

Weakness: CWE-345 (Insufficient Verification of Data Authenticity), CWE-1284 (Improper Validation of Specified Quantity in Input), CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-102711 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102711 is a medium-severity memory corruption vulnerability in `eclipse-threadx/threadx` (module manager / loadable-module loader), published on 29 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-102711 in the wild and no public exploit code.

Affected product: `eclipse-threadx/threadx` (module manager / loadable-module loader). 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-102711/ (Markdown: https://insights.sbomify.com/CVE-2026-102711/index.md)
```

## Sources

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

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