CVE-2026-113421: In Eclipse ThreadX versions 6.0.1 through 6.5.2.202603, ThreadX Modules does not revoke a module's trace-buffe

Routine

HIGH 7.3UPGRADE

CVE-2026-113421 is a high-severity flaw (CVSS 7.3) affecting eclipse threadx. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 m

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.3 (High)
EPSS exploit chance	n/a
CISA exploited list	No
Weakness	CWE-416
Published	2026-11-03
Last modified	2026-11-03

Publisher (CNA): eclipse · Vendor: eclipse foundation · Source: CVE Program record (NVD analysis pending)

Last updated 2026-11-03 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-11-03 08:27 UTCPublished CVE record published
2026-11-03 08:27 UTCUpdated Record last modified

eclipse foundation eclipse threadx UPGRADE

Affected: >= 6.0.1 and <= 6.5.2.202603

Fixed in: newer than 6.5.2.202603

Safe to downgrade to: a release before 6.0.1

1. Check installed version

apt-cache policy eclipse-threadx || rpm -q eclipse-threadx || eclipse-threadx --version

2. UPGRADE to newer than 6.5.2.202603 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade eclipse-threadx

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade eclipse-threadx

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 6.0.1 (Debian / Ubuntu)

apt-cache madison eclipse-threadx sudo apt install eclipse-threadx=<VERSION_BEFORE_6.0.1> sudo apt-mark hold eclipse-threadx

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list eclipse-threadx sudo dnf downgrade eclipse-threadx-<VERSION_BEFORE_6.0.1> sudo dnf versionlock add eclipse-threadx

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-113421?

eclipse threadx: upgrade to newer than 6.5.2.202603. Exact commands for each OS are on this page.

Is CVE-2026-113421 being exploited?

CVE-2026-113421 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-113421 affect?

CVE-2026-113421 affects eclipse threadx. Severity is high (CVSS 7.3). 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,

How urgent is CVE-2026-113421?

Priority 26/100. High severity

Related CVEs

CVE-2026-115231 HIGH 8.5 UPGRADE In Eclipse ThreadX versions 6.0.1 through 6.5.2.202603, the Module Manager lets a user-mode, memory-protected

References

← Back to latest CVEs