# CVE-2026-102709: Information disclosure in ThreadX

> Attackers in the non-secure world can read secure memory via improper pointer validation in ThreadX TrustZone-M functions, potentially exposing cryptographic keys.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-75rq-fmfg-xmgx, GHSA-ffg5-m7vh-vwrp

## What is CVE-2026-102709?

CVE-2026-102709 is a high-severity vulnerability in Eclipse Foundation ThreadX, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper validation of non-secure (NS) pointers in multiple TrustZone-M non-secure callable (NSC) entry functions allows an attacker executing in the non-secure world to supply pointers to secure memory. The secure firmware subsequently dereferences these attacker-controlled pointers without verifying that they reference non-secure memory, resulting in unintended disclosure of secure memory contents. This violates the isolation guarantees provided by Arm TrustZone-M and can be leveraged as a memory disclosure or corruption primitive that may enable recovery of sensitive cryptographic material.

Weakness: CWE-822 (Untrusted Pointer Dereference), CWE-501 (Trust Boundary Violation), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-102709?


## How do I fix CVE-2026-102709?

No fix has been published for CVE-2026-102709 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-102709 being exploited?

There is no known exploitation of CVE-2026-102709 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102709 and fix it if it is affected.

What it is: CVE-2026-102709 is a high-severity vulnerability in Eclipse Foundation ThreadX, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102709 in the wild and no public exploit code.

Affected product: Eclipse Foundation ThreadX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102709/ (Markdown: https://insights.sbomify.com/CVE-2026-102709/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102709
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102709
- OSV: https://osv.dev/vulnerability/CVE-2026-102709

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102709/
Summaries are generated and may contain mistakes; the official description above is the record.