Is CVE-2026-115654 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-115654 being exploited in the wild.

How severe is CVE-2026-115654?

Informational severity, published 2 November 2026.

Which products and versions are affected?

Eclipse ThreadX 6.0.1 through 6.5.2.202603.

How is CVE-2026-115654 attacked?

It is attacked with local access, in an operating system.

Am I affected by CVE-2026-115654?

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.

CVE-2026-115654: Eclipse ThreadX Module Manager missing authorization in thread control

CVE-2026-115654 · Severity: info · Published 2026-11-02

Eclipse ThreadX is a real-time kernel used in embedded systems and IoT devices to manage threads and system scheduling. A flaw in its Module Manager allows any loaded software module with memory protection to suspend, terminate, or change the priority of threads belonging to the application or other modules, causing service denial or unpredictable behavior. An attacker with the ability to load a malicious module could disable critical system functions or crash application threads.

Technologies: Eclipse ThreadX. Vendors: Eclipse.

Quick answers

Is CVE-2026-115654 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-115654 being exploited in the wild.
How severe is CVE-2026-115654?: 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-115654?: Yes: fixed in 6.5.2.202603b. Until then: Restrict the loading and execution of untrusted modules on systems using the Module Manager with memory protection. For applications that require module-to-application thread control, use shared synchronisation objects instead of direct thread manipulation. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-115654 attacked?: It is attacked with local access, in an operating system.
Am I affected by CVE-2026-115654?: 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: 6.5.2.202603b

Restrict the loading and execution of untrusted modules on systems using the Module Manager with memory protection. For applications that require module-to-application thread control, use shared synchronisation objects instead of direct thread manipulation.

Technical details

The Module Manager's thread-control dispatchers (_txm_module_manager_param_check_typed_object_for_use) validate that a thread pointer references a live thread outside the calling module, but do not verify ownership. A memory-protected module can therefore call tx_thread_suspend, tx_thread_resume, tx_thread_terminate, tx_thread_reset, tx_thread_priority_change, tx_thread_preemption_change, tx_thread_time_slice_change, and tx_thread_wait_abort on any thread in the system, using pointers obtained via txm_module_object_pointer_get_extended or tx_thread_info_get. This enables denial-of-service or manipulation of system scheduling without code execution or memory access.

Affected products

Eclipse ThreadX 6.0.1 through 6.5.2.202603

Timeline

2026-11-01: disclosed
2026-11-02: patched: ThreadX 6.5.2.202603b released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.