# CVE-2026-115231: Eclipse ThreadX Module Manager privilege escalation via forged callback

Source: https://junglewise.ai/threats/cve-2026-115231-in-eclipse-threadx-versions-6-0-1-through-6-5-2-202603-the  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-03. Updated: 2026-11-03  
License: CC BY 4.0 with a link back

CVE-2026-115231 · Severity: info · Published 2026-11-03

Eclipse ThreadX is a real-time operating system kernel used in embedded devices. A user-mode module can forge callback requests to another module's queue, causing that module's callback thread to execute attacker-controlled code with the target module's privileges. On devices where a privileged module is present, this allows a user-mode attacker to gain kernel-level execution, completely defeating the isolation provided by ThreadX's Module Manager.

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

## Quick answers

**Is CVE-2026-115231 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-115231 being exploited in the wild.

**How severe is CVE-2026-115231?** Informational severity, published 3 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-115231?** Yes: fixed in ThreadX 6.5.2.202603b. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-115231 attacked?** It is attacked with local access, in an operating system.

**Am I affected by CVE-2026-115231?** 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

## Technical details

A memory-protected user-mode module can post forged callback requests to another module's callback queue by walking the kernel queue list and sending messages to queues outside its own memory. The receiving module's callback worker thread calls function pointers from these messages without verifying they originated from the Module Manager, allowing arbitrary code execution in the target module's context. When the receiving module runs in privileged mode, this becomes a privilege escalation to kernel-level access.

## Affected products

- Eclipse ThreadX 6.0.1 through 6.5.2.202603

## Timeline

- 2026-11-01: disclosed: GitHub advisory GHSA-q2rc-f35r-2hw6 published
- 2026-11-03: advisory: CVE-2026-115231 published
- 2026-11-01: patched: Fix released in ThreadX 6.5.2.202603b

## References

- [https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-q2rc-f35r-2hw6](https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-q2rc-f35r-2hw6)
- [https://gitlab.eclipse.org/security/cve-assignment/-/work_items/484](https://gitlab.eclipse.org/security/cve-assignment/-/work_items/484)

## Related threats

- [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)
- [Eclipse ThreadX Cortex-A7 MMU Modules buffer validation bypass](https://junglewise.ai/threats/cve-2026-95109-the-cortex-a7-mmu-modules-port-validates-a-caller-supplied-buffer)