Memory disclosure via undersized block-pool parameter validation
Published Oct 20, 2026 · Updated Oct 20, 2026
Out-of-bounds reads in Eclipse ThreadX Modules allow local users to disclose boundary memory via block-pool creation. The _txm_module_manager_tx_block_pool_create_dispatch function validates two parameter words but reads four, including an unchecked pool size during buffer validation. Execution in a loaded, memory-protected module is required; disclosure is confined to adjacent words, and a memory fault terminates the requesting thread rather than the system.
Summary
What happened
Out-of-bounds reads in Eclipse ThreadX Modules allow local users to disclose boundary memory via block-pool creation. The _txm_module_manager_tx_block_pool_create_dispatch function validates two parameter words but reads four, including an unchecked pool size during buffer validation. Execution in a loaded, memory-protected module is required; disclosure is confined to adjacent words, and a memory fault terminates the requesting thread rather than the system.
The record
- CVE
- CVE-2026-94202
- Published
- Oct 20, 2026
- Updated
- Oct 20, 2026
- Vendor
- The Eclipse Foundation
- Product
- Eclipse ThreadX
- Classifications
- CWE-125
- 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