Skip to main content
veriom
Menu

Explore Veriom products, resources, and account pages.

CVE-2026-113780espressif esp-idf out-of-bounds write

Schedule itCritical9.3EPSS 0.14%, higher than 3% of scored CVEs

CVE-2026-113780 is a out-of-bounds write in espressif esp-idf, rated critical (9.3 on CVSS 3.1).

Why this priority: Critical severity, with no exploitation signal yet.

Published · Updated · NVD status: Received

What it is

Code writes past the end of a buffer, corrupting memory in ways an attacker can often turn into code execution. A pointer value from outside is used directly.

How it is reached

An attacker can exploit it by someone who can already run code or sign in on the machine, without an account, and nobody has to click anything.

What an attacker gains

A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker crash the process, read memory, or in the worst case run code. The damage can spread past the vulnerable component into others.

Is it being exploited?

There is no public report of exploitation yet. EPSS estimates a 0.14% chance of exploitation activity in the next 30 days, higher than 3% of scored CVEs.

What to do

  1. Upgrade espressif esp-idf to a fixed version for your release line (5.5.6, 6.0.4, 6.1.1).
  2. Limit who can run code or sign in on the hosts that run it.

Description from NVD

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 this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Native code: operating systems, browsers and firmware. The flaw sits wherever native code reads untrusted data.
  • Network appliances and media or file parsers. The flaw sits wherever native code reads untrusted data.

Trust boundaries in play

  • Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
  • Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
  • Wherever native code reads untrusted data. An attacker who crosses it can crash the process, read memory, or in the worst case run code.

Questions to answer about your own systems

  • Where does espressif esp-idf run in your systems, and at which version?
  • Which of those hosts also run code or users you do not fully trust?
  • What can it reach once compromised: which data stores, secrets and services?
See how Veriom maps an architectureTake the interactive tour

Read more

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.