Quick answers
- Is CVE-2026-115653 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115653 being exploited in the wild.
- How severe is CVE-2026-115653?
- 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-115653?
- Yes: fixed in ThreadX 6.5.2.202603b. Until then: Do not load untrusted user-mode memory-protected modules on systems using the Module Manager on Cortex-M ports, or restrict module capabilities and monitor stack pointer manipulation. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115653 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-115653?
- 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.202603b
Do not load untrusted user-mode memory-protected modules on systems using the Module Manager on Cortex-M ports, or restrict module capabilities and monitor stack pointer manipulation.
Technical details
The PendSV exception handler in Cortex-M module ports saves thread context (registers and exception return value) at addresses derived from the thread's program stack pointer without validating that pointer against the thread's actual stack bounds. A user-mode memory-protected module can set its stack pointer freely and cause privileged stores to memory it should not access, reading back kernel or application data during the next context switch. The vulnerability affects versions 6.0.1 through 6.5.2.202603 on Cortex-M0+, M3, M4, M7, M23, and M33 with the Module Manager enabled.
Affected products
- Eclipse ThreadX 6.0.1 through 6.5.2.202603
Timeline
- 2026-11-02: disclosed