Quick answers
- Is CVE-2026-118052 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118052 being exploited in the wild.
- How severe is CVE-2026-118052?
- Informational severity, published 2 November 2026.
- Which products and versions are affected?
- Eclipse ThreadX 6.0.1 through 6.5.2.202603.
- Is there a fix for CVE-2026-118052?
- Yes: fixed in ThreadX 6.5.2.202603b. Until then: Validate module preamble data and stack sizes before loading; restrict module loading to trusted sources; use module signing and verification to prevent loading of crafted images. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118052 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-118052?
- 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.
How to fix
- Fixed in: ThreadX 6.5.2.202603b
Validate module preamble data and stack sizes before loading; restrict module loading to trusted sources; use module signing and verification to prevent loading of crafted images.
Technical details
The Module Manager's internal load functions (_txm_module_manager_internal_load and _txm_module_manager_absolute_load_extended) take a mutex, compute module memory allocations from preamble fields using TXM_MODULE_MANAGER_UTIL_MATH_ADD_ULONG, and return directly on overflow without releasing the mutex. This creates a deadlock: other threads attempting module operations wait indefinitely for the held lock. The vulnerability requires local privilege (low) and affects systems loading untrusted module images.
Affected products
- Eclipse ThreadX 6.0.1 through 6.5.2.202603
Timeline
- 2026-11-01: disclosed
- 2026-11-02: advisory