Quick answers
- Is CVE-2026-94023 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-94023 being exploited in the wild.
- How severe is CVE-2026-94023?
- Informational severity, published 20 October 2026.
- Which products and versions are affected?
- Eclipse ThreadX 6.0.1 to 6.5.1.202602a.
- Is there a fix for CVE-2026-94023?
- 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-94023 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-94023?
- 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 Module Manager's delete dispatch functions fail to verify object ownership before performing irreversible deletion; ownership is checked only after the object is already unlinked from the system and all cleanup performed. Additionally, ownership verification involves a privileged read from an attacker-controlled address offset, causing potential out-of-bounds reads and writes through pointers from untrusted memory. A module with access to the delete API can supply a pointer to any kernel object and have it destroyed, bypassing synchronization semantics.
Affected products
- Eclipse ThreadX 6.0.1 to 6.5.1.202602a
Timeline
- 2026-10-02: disclosed
- 2026-10-20: advisory