The ESP-IDF framework contained a flaw where a local unprivileged REE application could control a write through the REE-supplied stack pointer before a switch to the trusted TEE stack. This unvalidated stack pointer allowed the REE program to reach TEE‑exclusive memory on ESP32‑C5, ESP32‑C6, ESP32‑C61, and ESP32‑H2 devices, breaking the isolation boundary. The consequence is potential corruption of TEE control‑flow data, which could lead to remote code execution, denial of service, or system crashes. The weakness aligns with CWE‑787 (Out‑of‑Bounds Write) and CWE‑822 (Buffer Unbound Write).

The affected products are Espressif’s ESP‑IDF IoT development framework. Versions from 5.5.5 up to, but not including, 5.5.6, as well as 6.0.4 and 6.1.1, contain the vulnerable ordering. Devices impacted are the ESP32‑C5, ESP32‑C6, ESP32‑C61, and ESP32‑H2. Any firmware built with these releases on the listed silicon is vulnerable.

With a CVSS score of 9.3 the vulnerability poses a high‑severity risk. The EPSS score is not available, and the vulnerability is not yet listed in CISA KEV. Attackers could exploit the issue locally from any REE code and leverage the untrusted stack pointer write to corrupt TEE memory. The exploit requires the attacker to have control over a non‑privileged REE application on the same device, making the risk highest in environments where untrusted user code runs on the device. The likely attack vector is a local REE application performing a crafted write before the privilege switch.