Kernel-object destruction via missing delete authorization
Published Oct 20, 2026 · Updated Oct 20, 2026
Authorization bypass in Eclipse ThreadX Modules lets local users delete unowned kernel objects through the Module Manager. Delete dispatchers check ownership after deletion, and the deallocator reads unchecked memory preceding the supplied object pointer. Releases 6.0.1 through 6.5.1.202602a require a loaded module and a Module Manager object pool; deletion breaks synchronization, while the unchecked read causes privileged faults.
Summary
What happened
Authorization bypass in Eclipse ThreadX Modules lets local users delete unowned kernel objects through the Module Manager. Delete dispatchers check ownership after deletion, and the deallocator reads unchecked memory preceding the supplied object pointer. Releases 6.0.1 through 6.5.1.202602a require a loaded module and a Module Manager object pool; deletion breaks synchronization, while the unchecked read causes privileged faults.
The record
- CVE
- CVE-2026-94023
- Published
- Oct 20, 2026
- Updated
- Oct 20, 2026
- Vendor
- The Eclipse Foundation
- Product
- Eclipse ThreadX
- Classifications
- CWE-862, CWE-125, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 20, 2026CVE publishedPublication date reported by the CVE source.
- Oct 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.0.1 <=6.5.1.202602a
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us