CVE-2026-102709

published 29 Sep 2026 · updated 3 Nov 2026

In Eclipse ThreadX versions 6.0.1 through 6.5.2.202603, the four non-secure-callable secure stack functions of the TrustZone-M ports…

8.4HighCVSS 8.4EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

In Eclipse ThreadX versions 6.0.1 through 6.5.2.202603, the four non-secure-callable secure stack functions of the TrustZone-M ports dereference a thread pointer supplied by the non-secure world without checking that it points to non-secure memory. Non-secure code can make the secure firmware reveal which secure bytes are zero, write chosen secure words, and fault the secure world, breaking TrustZone-M isolation and enabling recovery of secure-world secrets such as cryptographic keys.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Eclipse Foundation>=6.0.1 <=6.5.2.202603

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-102709 severity on Zeptric[![CVE-2026-102709](https://zeptric.io/badge/cve/CVE-2026-102709.svg)](https://zeptric.io/cve/CVE-2026-102709)