# CVE-2026-113421: ThreadX Modules invokes trace-full callbacks after module unload


- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 3 Nov 2026
- **Also known as:** GHSA-8pgj-qvjv-j4fq

## What is CVE-2026-113421?

CVE-2026-113421 is a high-severity vulnerability in Eclipse ThreadX, published on 3 Nov 2026. 

### Official description

In Eclipse ThreadX versions 6.0.1 through 6.5.2.202603, ThreadX Modules does not revoke a module's trace-buffer-full callback when the module is stopped and unloaded. With event tracing enabled and a kernel-owned trace buffer still active, a later buffer wrap invokes the callback from privileged thread context after the module's code has been released, so a user-mode module can have its code run with kernel privileges after unload, or, once the memory is reused, redirect control flow or cause a fault.

Weakness: CWE-416 (Use After Free)

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


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

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

## Is CVE-2026-113421 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113421 is a high-severity vulnerability in Eclipse ThreadX, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-113421 in the wild and no public exploit code.

Affected product: Eclipse 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-113421/ (Markdown: https://insights.sbomify.com/CVE-2026-113421/index.md)
```

## Sources

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

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