Quick answers
- Is CVE-2026-94202 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-94202 being exploited in the wild.
- How severe is CVE-2026-94202?
- 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-94202?
- Yes: fixed in ThreadX 6.5.2.202603. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-94202 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-94202?
- 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
Technical details
The `_txm_module_manager_tx_block_pool_create_dispatch` function validates only 2 of 4 ALIGN_TYPE words in an extra-parameter array before reading all 4 words, resulting in two-word out-of-bounds reads. The vulnerability exists in the validation layer itself (indices 1–2 used for bounds-checking a caller buffer, but index 2 itself is unvalidated) and when building the kernel service call (index 3 also unvalidated). A malicious or compromised low-privilege module can exploit this by passing a pointer to an array with controlled layout to read kernel memory immediately past an approved region.
Affected products
- Eclipse ThreadX 6.0.1 through 6.5.1.202602a
Timeline
- 2026-10-20: advisory