CVE-2026-95107

Module object allocation size overflow corrupts the manager object pool

  • High 7.0

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.

Key facts

Published
20 Oct 2026
Last changed
20 Oct 2026
Assigned by
eclipse
EPSS
0.154% likely to be exploited in the next 30 days, higher than 4.565% of CVEs (scores for 18 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.0CVSS 4.0, Highfrom the CNA (eclipse)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

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Eclipse FoundationEclipse ThreadX
  • Default status: unaffected
  • 6.0.1 up to and including 6.5.1.202602a (affected)
  • 6.5.2.202603 (unaffected)

Timeline

  1. 20 Oct 2026 Published

Weakness

References