CVE-2026-95107

published 20 Oct 2026 · updated 20 Oct 2026

Module object allocation size overflow corrupts the manager object pool

7.0HighCVSS 7.0EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Eclipse Foundation>=6.0.1 <=6.5.1.202602a

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-95107 severity on Zeptric[![CVE-2026-95107](https://zeptric.io/badge/cve/CVE-2026-95107.svg)](https://zeptric.io/cve/CVE-2026-95107)