# CVE-2026-95107: ThreadX Module Manager integer overflow in object allocation

Source: https://junglewise.ai/threats/cve-2026-95107-a-threadx-module-chooses-object-size-when-it-calls-txm-module  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-20. Updated: 2026-10-20  
License: CC BY 4.0 with a link back

CVE-2026-95107 · Severity: info · Published 2026-10-20

Eclipse ThreadX is a real-time operating system kernel used in embedded and IoT devices. The Module Manager component contains an integer overflow flaw when allocating memory for modules, allowing a low-privilege module to corrupt shared memory structures and trigger denial of service affecting the entire system and all running modules.

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

## Quick answers

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

**How severe is CVE-2026-95107?** Informational severity, published 20 October 2026.

**Which products and versions are affected?** Eclipse ThreadX 6.0.1 through 6.5.1.202602a.

**Is there a fix for CVE-2026-95107?** Yes: fixed in ThreadX 6.5.2.202603. Until then: Disable the TXM_MODULE_OBJECT_ALLOCATE_CALL build option if module object allocation is not required, or restrict module loading to trusted sources only. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-95107 attacked?** It is attacked with local access, in an operating system.

**Am I affected by CVE-2026-95107?** 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.202603

Disable the TXM_MODULE_OBJECT_ALLOCATE_CALL build option if module object allocation is not required, or restrict module loading to trusted sources only.

## Technical details

An integer overflow occurs in _txm_module_manager_object_allocate when adding a 16-byte header size to a caller-controlled object_size without overflow checking; on 32-bit systems, sizes near ULONG_MAX wrap to small values, causing undersized allocations followed by out-of-bounds writes into neighbouring memory blocks. This corrupts byte-pool metadata and allows an attacker to inject arbitrary pointers into the pool's block list, leading to privileged writes outside the pool or information disclosure through address equality probes.

## Affected products

- Eclipse ThreadX 6.0.1 through 6.5.1.202602a

## Timeline

- 2026-10-02: disclosed: GitHub security advisory published
- 2026-10-20: advisory: Publicly documented in NVD

## References

- [https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-63qc-jcr6-qw6r](https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-63qc-jcr6-qw6r)

## 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)