CVE-2026-95107

Module object allocation size overflow corrupts the manager object pool

HIGH
7
CVSS Score
Published: October 20, 2026 at 03:20 PM UTC
Updated: October 20, 2026 at 07:48 PM UTC
1 product affected across 1 vendorThreadX

Using Eclipse ThreadX by Eclipse Foundation?

Get instant alerts when new vulnerabilities affect Eclipse ThreadX - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Vendor states this is fixed in 6.5.2.202603 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7HIGHeclipse
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-190CWE-680CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card