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