# CVE-2026-102711: Eclipse ThreadX loadable-module loader heap read overflow

Source: https://junglewise.ai/threats/cve-2026-102711-two-issues-in-the-threadx-loadable-module-loader-reached-when-a  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-29. Updated: 2026-09-29  
License: CC BY 4.0 with a link back

CVE-2026-102711 · Severity: info · Published 2026-09-29

Eclipse ThreadX is a real-time operating system kernel used in embedded and IoT devices. When a device loads a malicious module via the loadable-module APIs, two memory safety issues allow attackers to read beyond allocated memory boundaries and bypass pointer validation checks, potentially enabling information disclosure or code execution on the device.

Technologies: [Eclipse ThreadX](https://junglewise.ai/threats/technologies/threadx). Vendors: [Eclipse](https://junglewise.ai/threats/vendors/eclipse).

## Quick answers

**Is CVE-2026-102711 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-102711 being exploited in the wild.

**How severe is CVE-2026-102711?** Informational severity, published 29 September 2026.

**Which products and versions are affected?** Eclipse ThreadX <UNKNOWN>.

**Is there a fix for CVE-2026-102711?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-102711 attacked?** It is attacked with local access, in a software library.

**Am I affected by CVE-2026-102711?** Check whether you run Eclipse ThreadX at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability exists in the module loader APIs `_txm_module_manager_memory_load` and `_txm_module_manager_in_place_load`, which accept only a base pointer without image length validation. All size and offset fields from the TXM_MODULE_PREAMBLE structure are attacker-controlled: (1) a heap out-of-bounds read occurs because code_size is used as the source-image length in the copy loop without bounds checking, and (2) module entry/start/callback/stop function pointers are computed via simple offset arithmetic without cryptographic checksum verification, enabling pointer hijacking. No controlled out-of-bounds write was identified.

## Affected products

- Eclipse ThreadX <UNKNOWN>

## Timeline

- 2026-09-29: disclosed

## References

- [https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-f53h-37j4-mqxx](https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-f53h-37j4-mqxx)

## Related threats

- [Eclipse ThreadX Module Manager privilege escalation via forged callback](https://junglewise.ai/threats/cve-2026-115231-in-eclipse-threadx-versions-6-0-1-through-6-5-2-202603-the)
- [Eclipse ThreadX Modules use-after-free in trace-buffer callback](https://junglewise.ai/threats/cve-2026-113421-in-eclipse-threadx-versions-6-0-1-through-6-5-2-202603-threadx)
- [Eclipse ThreadX Module Manager missing authorization in thread control](https://junglewise.ai/threats/cve-2026-115654-in-eclipse-threadx-versions-6-0-1-through-6-5-2-202603-the)
- [Eclipse ThreadX Cortex-M stack pointer memory access in privileged mode](https://junglewise.ai/threats/cve-2026-115653-in-eclipse-threadx-versions-6-0-1-through-6-5-2-202603-the)
- [Eclipse ThreadX Module Manager mutex deadlock in preamble size validation](https://junglewise.ai/threats/cve-2026-118052-in-eclipse-threadx-versions-6-0-1-through-6-5-2-202603-the)