CVE-2026-95108 Eclipse Foundation CVE debrief

Who should care

Defenders responsible for Eclipse ThreadX module manager deployments should assess exposure and verify affected versions. System administrators and security teams should monitor system resources to detect potential exhaustion of the shared object pool.

Why it matters

Defenders should care about this vulnerability as it can cause a memory leak, leading to exhaustion of the shared object pool, and preventing other modules from creating kernel objects or user-mode module threads. Verification of affected versions and application of patches or updates is necessary.

• Memory leak can cause exhaustion of the shared object pool
• Prevents other modules from creating kernel objects or user-mode module threads
• Requires verification of affected versions and application of patches or updates

Technical summary

The Eclipse ThreadX module manager has a memory leak vulnerability in the `_txm_module_manager_tx_thread_delete_dispatch` function. When a user-mode module thread is deleted, its privileged kernel stack is not released, leading to a memory leak. This can cause the shared object pool to be exhausted, preventing other modules from creating kernel objects or user-mode module threads. The vulnerability affects Eclipse ThreadX module manager deployments, and defenders should review and update the module manager to fix the memory leak vulnerability. Verification of affected versions and application of patches or updates is necessary to prevent potential exhaustion of the shared object pool.

Defensive priority

Medium

Recommended defensive actions

• Review and update Eclipse ThreadX module manager to fix the memory leak vulnerability
• Verify affected versions and apply patches or updates as needed
• Monitor system resources to detect potential exhaustion of the shared object pool
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and source item provide details about the vulnerability, including its description, affected versions, and references. However, the corpus does not establish versions, exploitation, impact, or remediation, which require verification from the supplied official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.