TI-2026-76894 Aliases CVE-2026-94023

Eclipse ThreadX modules can delete kernel objects they do not own

LOW 29CWE-125Published 2026-10-20 · Updated 2026-10-20

Key facts

Attack vector: Local
Privileges required: Low
User interaction: None
Attack complexity: Low
Attack requirements: None
Impact type: Security bypass
Confidentiality · integrity · availability: None · High · High
Fix status: Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-862.

Summary

Eclipse ThreadX from 6.0.1 through 6.5.1.202602a is affected. The Module Manager delete dispatchers check only that an object lies outside the module's own code and data, so they do not verify ownership before deleting a kernel object (CWE-862). A local attacker with low privileges can have the privileged dispatcher delete objects created by others, and the deletion cannot be undone.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Description from the CNA

A ThreadX module reaches a kernel object's delete service through the Module Manager's dispatch layer, which asked one question about the pointer: does the object lie outside the module's own code and data. That is the policy for *using* an object, and using an object a module does not own is supported and intended — `txm_module_object_pointer_get_extended` searches the system's created objects by name and hands back objects the application created and objects other modules created, so that a module can send to a shared queue, take a shared semaphore or get a shared mutex. Destroying one of those is not sharing it. A module could name any object it had a pointer to and have the privileged dispatcher delete it.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV

EPSS 0.00129 2nd percentileScored 2026-11-07

Fix Fixed Eclipse ThreadX (Eclipse Foundation): 6.5.2.202603

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation: None
Automatable: No
Technical impact: Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

Vendor	Product	Affected versions	Fixed in	Status	Source
Eclipse Foundation	Eclipse ThreadX	6.0.1 – 6.5.1.202602a	6.5.2.202603	Patch available	CNA

Eclipse ThreadX VendorEclipse Foundation Affected 6.0.1 – 6.5.1.202602a Fixed in 6.5.2.202603 Patch available CNA

Remediation

Eclipse ThreadX 6.5.2.202603 fixes this flaw. Upgrade affected installations to that version.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Fix · CNA Eclipse ThreadX (Eclipse Foundation) Fixed in 6.5.2.202603

Timeline

2026-10-20 Threatist record created from CVE-2026-94023
2026-10-20 CISA SSVC decision points changed
2026-10-20 Priority changed: MEDIUM → LOW

References

Other 1

https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-36vf-7cx6-9f9j

TI-2023-23979 The HTTP/2 protocol allows a denial of service (server resource consumption) because… KEVCVSS 3.1HIGH 7.5
TI-2026-81947 Unauthenticated command injection in Eclipse Che che-machine-exec CVSS 3.1CRITICAL 9.8
TI-2026-13216 CWE-863: ABAC authorization bypass via trailing slash route normalization in Eclipse BaSyx Go Components CVSS 3.1CRITICAL 9.8
TI-2026-06514 Path traversal in Eclipse BaSyx CVSS 3.1CRITICAL 10.0
TI-2026-01382 In the Eclipse Theia Website repository, the GitHub Actions workflow… CVSS 3.1CRITICAL 10.0
TI-2026-74697 Authentication bypass in Eclipse Jetty EthereumAuthenticator CVSS 4.0CRITICAL 9.3

See all 466 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences