CVE-2026-95107: Module object allocation size overflow corrupts the manager object pool
Eclipse Foundation · Eclipse ThreadX
Vendor fix available · Affected: Eclipse Foundation Eclipse ThreadX · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 4% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Eclipse Foundation · Eclipse ThreadXfrom 6.0.1 up to and including 6.5.1.202602a
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Eclipse Foundation
- Published
- October 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-95107 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.