PoC Monitor
← All CVEs
CVE-2026-102757published 29 Sep 2026 17:24 UTCData: JSON · API

Eclipse Foundation ThreadX

An unprivileged, memory-protected ThreadX module can have the kernel read and write memory at addresses of its choosing, in privileged mode, and can use that to clear the MPU enable bit and remove its own isolation boundary. The Module Manager decided whether a privileged service could dereference an object address a module named by asking only whether that address fell outside the module. The manager's object pool is outside every module, so the test was satisfied by an address shifted into the interior of one of the module's own privileged allocations, which denotes no object at all. The bytes such an address presents as a control block are bytes the module put there through ordinary create and set services, so the control block ID at the front of them could be made to read as any type the module chose, and the `_txe_` layer's ID test then agreed. The reported chain uses that to reach a privileged `memset` across an attacker-chosen range.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.5high · scored by CNA · CWE-125
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Eclipse Foundation ThreadX
  • >= 6.0.1, <= 6.5.1.202602a

Fixed in 6.5.2.202603

Mitigation

Upgrade ThreadX to 6.5.2.202603 or later.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published29 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.