Quick answers
- Is CVE-2026-102709 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102709 being exploited in the wild.
- How severe is CVE-2026-102709?
- Informational severity, published 29 September 2026.
- Which products and versions are affected?
- Arm TrustZone-M <UNKNOWN>.
- Is there a fix for CVE-2026-102709?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-102709 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-102709?
- Check whether you run Arm TrustZone-M at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in TrustZone-M non-secure callable (NSC) entry functions that fail to validate whether pointers supplied by non-secure code actually reference non-secure memory regions. Secure code dereferences these attacker-controlled pointers without bounds checking, allowing disclosure or corruption of secure memory. This violates TrustZone-M's memory isolation guarantees and can be leveraged to extract sensitive cryptographic material.
Affected products
- Arm TrustZone-M <UNKNOWN>
Timeline
- 2026-09-29: disclosed