# CVE-2026-102710: Eclipse ThreadX privilege escalation in trace callback

Source: https://junglewise.ai/threats/cve-2026-102710-attacker-model-preconditions-a-loaded-txm-module-user-mode-txm  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-29. Updated: 2026-09-29  
License: CC BY 4.0 with a link back

CVE-2026-102710 · Severity: info · Published 2026-09-29

Eclipse ThreadX is an embedded real-time operating system kernel used in IoT and embedded devices. A user-mode module can register an arbitrary function pointer as a trace callback that executes with kernel privileges when the trace buffer wraps, allowing privilege escalation or denial of service.

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

## Quick answers

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

**How severe is CVE-2026-102710?** Informational severity, published 29 September 2026.

**Which products and versions are affected?** Eclipse ThreadX builds with TX_ENABLE_EVENT_TRACE.

**Is there a fix for CVE-2026-102710?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-102710 attacked?** It is attacked with local access, in a software library.

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

## Technical details

A user-mode, memory-protected module can register an arbitrary function pointer as the global trace-full callback via kernel dispatch calls. The kernel invokes this callback directly from privileged code without validation when the trace buffer wraps, allowing execution with kernel privilege. An invalid pointer causes kernel fault (DoS); a valid pointer into module code executes with kernel privilege (nPRIV=0).

## Affected products

- Eclipse ThreadX builds with TX_ENABLE_EVENT_TRACE

## Timeline

- 2026-09-29: disclosed

## References

- [https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-xr9m-8j99-rw4m](https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-xr9m-8j99-rw4m)

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