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

Status: published. Published: 2026-11-03. Updated: 2026-11-03.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Eclipse Foundation / Eclipse ThreadX: ≥ 6.0.1; ≤ 6.5.2.202603 (affected, custom). Source: CNA: eclipse

## Severity and prioritization

- CVSS 4.0: 7.3 (high); 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; source: CNA: eclipse

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-416

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-8pgj-qvjv-j4fq (CNA: eclipse)

- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/457 (CNA: eclipse)

## Provenance

- CNA: eclipse: https://www.cve.org/CVERecord?id=CVE-2026-113421; retrieved 2026-11-03; source updated 2026-11-03

Revision: cc3ded382e44bd7ff805690d4ba88a8329374e5e53ae2b47e3bb1c54586ea13a

Canonical: https://y2.dev/cve/CVE-2026-113421

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.