# CVE-2026-94023: Eclipse ThreadX module delete dispatch ownership enforcement

Source: https://junglewise.ai/threats/cve-2026-94023-a-threadx-module-reaches-a-kernel-object-s-delete-service-through  
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-94023 · Severity: info · Published 2026-10-20

Eclipse ThreadX is a real-time operating system kernel used in embedded and IoT devices. A low-privilege module can exploit the Module Manager's dispatch layer to destroy kernel objects (queues, semaphores, mutexes, timers, pools) that belong to the system or other modules, breaking inter-module synchronization and causing those waiting on deleted objects to be awakened with error conditions. This undermines system stability and could leave the device in an unrecoverable state.

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

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

## References

- [https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-36vf-7cx6-9f9j](https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-36vf-7cx6-9f9j)

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