CVE-2026-0648

Memory corruption via unchecked counter allocation failure

Published Jan 27, 2026 · Updated Jan 27, 2026

Memory corruption in Eclipse ThreadX 6.1.7 through 6.4.3 allows local users to write invalid memory by exhausting the OSEK counter pool. CreateCounter() tests osek_get_counter() failure against zero instead of E_OS_SYS_STACK, then casts that error value to OSEK_COUNTER * and writes through it. Repeated counter creation must first deplete the fixed pool; the resulting wild pointer can corrupt memory or trigger an immediate HardFault.

CVSS severity7.8
High
EPSS probability0.11%
Next 30 days · Sep 16, 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.

Book a demo

Summary

What happened

Memory corruption in Eclipse ThreadX 6.1.7 through 6.4.3 allows local users to write invalid memory by exhausting the OSEK counter pool. CreateCounter() tests osek_get_counter() failure against zero instead of E_OS_SYS_STACK, then casts that error value to OSEK_COUNTER * and writes through it. Repeated counter creation must first deplete the fixed pool; the resulting wild pointer can corrupt memory or trigger an immediate HardFault.

The record

CVE
CVE-2026-0648
Published
Jan 27, 2026
Updated
Jan 27, 2026
Vendor
The Eclipse Foundation
Product
Eclipse ThreadX
Classifications
CWE-253, CWE-787, T1499
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jan 27, 2026CVE publishedPublication date reported by the CVE source.
  2. Jan 27, 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.1.7 <=6.4.3

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Eclipse Foundation · Eclipse ThreadXversion=6.1.7 <=6.4.3

Published CVSS scores

6.3NIST National Vulnerability DatabaseCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H
7.8Eclipse FoundationCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

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.

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

No observations available

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

Weakness, pattern, technique

CWE-253Incorrect Check of Function Return Value
CWE-787Out-of-bounds Write
T1499Endpoint Denial of Service

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

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo