---
id: "CVE-2026-95107"
kind: "vulnerability"
aliases: ["CVE-2026-95107"]
title: "ThreadX: unchecked size addition lets a module corrupt adjacent memory"
severity: "high"
cvss: 7.0
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["embedded", "infrastructure", "module-manager", "rtos", "threadx"]
not_affected_if: ["module-manager-unused"]
published_at: "2026-10-20T16:17:18+00:00"
first_seen_at: "2026-10-23T21:57:20+00:00"
updated_at: "2026-10-25T03:38:21+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-95107", "first_seen_at": "2026-10-23T21:57:20+00:00"}]
---

# ThreadX: unchecked size addition lets a module corrupt adjacent memory

The ThreadX Module Manager adds a 16-byte header to a caller-chosen object size without checking for integer overflow. A size near the top of a ULONG wraps around, so the pool hands out a block too small for the header and the header write spills into neighbouring memory.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check whether the ThreadX version in use includes the Module Manager (`txm_module_object_allocate` in the build)
- unknown for the exact affected version range, as the sources do not say

## Fix

- Update ThreadX to a release that includes the fix for this issue (version unknown from the sources)
- Check the vendor advisory for the patched version

## Timeline

- 2026-10-23T21:57:20+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-95107

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_