CVE-2026-95107

Memory corruption via unchecked allocation-size addition

Published Oct 20, 2026 · Updated Oct 20, 2026

Integer overflow in Eclipse ThreadX Module Manager allows local users to corrupt kernel memory via crafted object-allocation sizes. The _txm_module_manager_object_allocate function adds a private header without checking for overflow, then writes that header beyond the undersized allocation into neighboring pool metadata. Exploitation requires a loaded low-privilege module, an object pool, and the enabled allocation service in 6.0.1 through 6.5.1.202602a; allocator corruption causes privileged faults and denial of service requiring reboot.

CVSS severity7.0
High
EPSS probability0.15%
Next 30 days · Nov 22, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Contact us

Summary

What happened

Integer overflow in Eclipse ThreadX Module Manager allows local users to corrupt kernel memory via crafted object-allocation sizes. The _txm_module_manager_object_allocate function adds a private header without checking for overflow, then writes that header beyond the undersized allocation into neighboring pool metadata. Exploitation requires a loaded low-privilege module, an object pool, and the enabled allocation service in 6.0.1 through 6.5.1.202602a; allocator corruption causes privileged faults and denial of service requiring reboot.

The record

CVE
CVE-2026-95107
Published
Oct 20, 2026
Updated
Oct 20, 2026
Vendor
The Eclipse Foundation
Product
Eclipse ThreadX
Classifications
CWE-680, CWE-787, CWE-190, T1499.004
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Oct 20, 2026CVE publishedPublication date reported by the CVE source.
  2. Oct 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.0.1 <=6.5.1.202602a

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Eclipse Foundation · Eclipse ThreadXversion=6.0.1 <=6.5.1.202602a

Published CVSS scores

7.0Eclipse ThreadXCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-680Integer Overflow to Buffer Overflow
CWE-787Out-of-bounds Write
CWE-190Integer Overflow or Wraparound
T1499.004Application or System Exploitation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Contact us