CVE-2026-95107Module object allocation size overflow corrupts the manager object pool
Updated under an hour ago ()
Does this affect you?
It affects Eclipse Foundation Eclipse ThreadX. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
A ThreadX module chooses `object_size` when it calls `txm_module_object_allocate`. The Module Manager adds its own 16-byte private header to that size and asked the object pool for the result **without checking the addition**. A size near the top of a `ULONG` wrapped, the pool served a block far smaller than the header, and the manager then wrote the header past the end of it and into the neighbouring byte-pool block.
- CVSS
- 7.0 HIGH (v4.0, CNA)CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N
- Weakness (CWE)
- CWE-190, CWE-680, CWE-787
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- eclipse
- NVD analysis
- Awaiting Analysis
- Record last updated
- Oct 20, 2026
- First seen by InfoSec Signals
- Oct 20, 2026
Affected products
Eclipse Foundation Eclipse ThreadX eclipse_foundation:eclipse_threadx (from the name) | from 6.0.1 through 6.5.1.202602a; 6.5.2.202603 not affected | CNA record |
References
- https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-63qc-jcr6-qw6r
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.