ESF-IDF: Unvalidated Stack Pointer at the ESP-TEE Privilege-Switch Boundary
Affects ESP-IDF before 5.5.6, 6.0.0 through 6.0.3, and 6.1.0 on ESP32-C5, ESP32-C6, ESP32-C61 and ESP32-H2 with ESP-TEE support. Fixed in 5.5.6, 6.0.4 and 6.1.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.5.6, 6.0.4, 6.1.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected SoCs with ESP-TEE support: ESP32-C5, ESP32-C6, ESP32-C61, ESP32-H2.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
CVE-2026-113780 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.3 (critical) and affects esp-idf; fixed in 5.5.6, 6.0.4 and 6.1.1.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 14/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 5.5.6, 6.0.4, 6.1.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
ESF-IDF, Espressif's IoT Development Framework, has a flaw in its ESP-TEE trap entry on ESP32-C5, ESP32-C6, ESP32-C61, and ESP32-H2 devices, where it saves a caller-controlled register frame through the REE-supplied stack pointer before validating it. A local, unprivileged application running in the REE (Rich Execution Environment) with no login required can use this to write into TEE-exclusive memory, which could break the REE/TEE isolation and potentially allow code execution, denial of service, or crashes.
Read the original description
ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. From 5.5.5 until 5.5.6, 6.0.4, and 6.1.1, the esp_tee trap entry in esp_tee_vectors_plic.S and esp_tee_vectors_clic.S saves a caller-controlled register frame through the REE-supplied stack pointer before switching to the trusted TEE stack or validating the pointer. A local unprivileged REE application can direct this machine-mode write into TEE-exclusive memory on ESP32-C5, ESP32-C6, ESP32-C61, and ESP32-H2 devices, breaking the REE/TEE isolation boundary and potentially corrupting TEE control-flow data for code execution, denial of service, or system crashes. Both secure-service ecall and interrupt entry paths contain the vulnerable ordering. This issue is fixed in version 5.5.6 and is scheduled to be fixed in versions 6.0.4 and 6.1.1.
What to do
Check whether your setup matches what the bug needs.
Affected SoCs with ESP-TEE support: ESP32-C5, ESP32-C6, ESP32-C61, ESP32-H2.Upgrade to a fixed version: 5.5.6, 6.0.4, 6.1.1.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- espressif esp-idf
fixed in 5.5.6; From 6.0.0 · fixed in 6.0.4; From 6.1.0 · fixed in 6.1.1
Evidence 6
- Advisory
- Repository
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-113780
Is CVE-2026-113780 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An unprivileged application running in the normal world (REE) can direct the ESP-TEE trap entry to write attacker-influenced content into TEE-resident memory, which breaks the isolation between REE and TEE. The advisory says this could potentially be escalated to arbitrary code execution inside the TEE, and may also cause memory corruption, denial of service or crashes.Source: github.com
Which versions are affected by CVE-2026-113780?
esp-idf: before 5.5.6; from 6.0.0 before 6.0.4; from 6.1.0 before 6.1.1.Source: cve.now feed data
Am I affected, and how do I check?
Affected are ESP-IDF versions before 5.5.6, 6.0.0 up to but not including 6.0.4, and 6.1.0 up to but not including 6.1.1, on ESP32-C5, ESP32-C6, ESP32-C61 and ESP32-H2 SoCs with ESP-TEE support. To check, look at the ESP-IDF version in use and the target chip the build is for.Source: github.com
How do I fix CVE-2026-113780?
On the 5.5 line, upgrade to ESP-IDF 5.5.6. On the 6.0 and 6.1 lines, the advisory names 6.0.4 and 6.1.1 as the fixed releases, but it states that both were yet to be released when it was written, so check for their availability before upgrading.Source: github.com