CVE-2026-95107
Received Received - Intake

ThreadX Module Manager Memory Corruption via Size Wrapping

Vulnerability report for CVE-2026-95107, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-20

Last updated on: 2026-10-20

Assigner: Eclipse Foundation

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-20
Last Modified
2026-10-20
Generated
2026-10-20
AI Q&A
2026-10-20
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Eclipse Foundation Eclipse ThreadX 6.0.1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-190 The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
CWE-787 The product writes data past the end, or before the beginning, of the intended buffer.
CWE-680 The product performs a calculation to determine how much memory to allocate, but an integer overflow can occur that causes less memory to be allocated than expected, leading to a buffer overflow.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability occurs in Eclipse ThreadX when a module allocates memory. The Module Manager adds a 16-byte header to the requested size without checking if the total size overflows. If the size wraps around near the top of a ULONG, the allocated block becomes too small, causing the header to overwrite adjacent memory in the byte pool.

Impact Analysis

This flaw could lead to memory corruption, crashes, or arbitrary code execution. Attackers might exploit it to gain control over the system, disrupt operations, or escalate privileges if the vulnerable ThreadX module is used in a critical application.

Mitigation Strategies

Apply the latest patches or updates from Eclipse Foundation for Eclipse ThreadX to fix the object allocation issue in the Module Manager. Ensure the fix addresses the size calculation and header addition checks.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-95107. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart