# CVE-2026-102710: Privilege escalation in eclipse-threadx/threadx

> A user-mode module can register a malicious callback executed with kernel privileges, enabling privilege escalation or denial of service.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-f447-c7m5-8f96, GHSA-xr9m-8j99-rw4m

## What is CVE-2026-102710?

CVE-2026-102710 is a critical vulnerability in eclipse-threadx/threadx, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Attacker model / Preconditions: a loaded `TXM_MODULE_USER_MODE | TXM_MODULE_MEMORY_PROTECTION` module issuing kernel dispatch calls, on a build with `TX_ENABLE_EVENT_TRACE`.

A user-mode, memory-protected module can register an arbitrary function pointer as the global trace-full callback. The kernel calls it directly — no validation, no trampoline — from privileged kernel code when the trace buffer wraps.

An invalid pointer faults the kernel (DoS). A pointer into the module's own code was observed running with kernel privilege (`CONTROL.nPRIV = 0`), confirmed at runtime with a register capture inside that code.

Weakness: CWE-822 (Untrusted Pointer Dereference), CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-102710?


## How do I fix CVE-2026-102710?

No fix has been published for CVE-2026-102710 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-102710 being exploited?

There is no known exploitation of CVE-2026-102710 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102710 and fix it if it is affected.

What it is: CVE-2026-102710 is a critical vulnerability in eclipse-threadx/threadx, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102710 in the wild and no public exploit code.

Affected product: eclipse-threadx/threadx. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102710/ (Markdown: https://insights.sbomify.com/CVE-2026-102710/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102710
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102710
- OSV: https://osv.dev/vulnerability/CVE-2026-102710

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102710/
Summaries are generated and may contain mistakes; the official description above is the record.