---
id: CVE-2026-95107
title: Module object allocation size overflow corrupts the manager object pool
summary: >-
  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 nea…
severity: high
cvss: 7
cvssVector: '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'
cvssSource: cna
cwe:
  - CWE-190
  - CWE-680
  - CWE-787
vendor: Eclipse Foundation
product: ThreadX
affected:
  - ThreadX >= 6.0.1 <= 6.5.1.202602a
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-10-20T17:05:27.399674Z'
published: '2026-10-20'
updated: '2026-10-20'
sourceUpdated: '2026-10-20T17:05:35.811Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-95107'
references:
  - url: >-
      https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-63qc-jcr6-qw6r
tags:
  - cve.org
ingestedAt: '2026-10-20T16:10:53.315Z'
---

## Overview

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

- `ThreadX >= 6.0.1 <= 6.5.1.202602a`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.