Known vulnerabilities in ESP-IDF v5.5
Which CVEs affect the components ESP-IDF v5.5 ships, such as mbed TLS, lwIP and cJSON, according to Espressif's own checker, and in which later release they are no longer reported.
21 known vulnerabilities reported for the components of ESP-IDF v5.5: 6 critical, 6 high, 8 medium, 1 low. Checked on 2026-11-12 with Espressif's esp-idf-sbom 1.4.0.
The newest release of this line is v5.5.6, with 6 known vulnerabilities reported (4 high, 2 medium).
Known vulnerabilities
| CVE | Component | Severity | What it is | In later 5.5 releases |
|---|---|---|---|---|
| CVE-2025-47917 | mbed_tls 3.6.3 | critical 9.8 | Mbed TLS before 3.6.4 allows a use-after-free in certain situations of applications that are developed in accordance with the documentation. | not reported in v5.5.1 |
| CVE-2026-34875 | mbed_tls 3.6.3 | critical 9.8 | An issue was discovered in Mbed TLS through 3.6.5 and TF-PSA-Crypto 1.0.0. | not reported in v5.5.5 |
| CVE-2026-34877 | mbed_tls 3.6.3 | critical 9.8 | An issue was discovered in Mbed TLS versions from 2.19.0 up to 3.6.5, Mbed TLS 4.0.0. | not reported in v5.5.5 |
| CVE-2025-66409 | esp-idf 5.5.0 | critical 9.1 | ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. | not reported in v5.5.2 |
| CVE-2026-34872 | mbed_tls 3.6.3 | critical 9.1 | An issue was discovered in Mbed TLS 3.5.x and 3.6.x through 3.6.5 and TF-PSA-Crypto 1.0. | not reported in v5.5.5 |
| CVE-2026-34873 | mbed_tls 3.6.3 | critical 9.1 | An issue was discovered in Mbed TLS 3.5.0 through 4.0.0. | not reported in v5.5.5 |
| CVE-2025-52496 | mbed_tls 3.6.3 | high 7.8 | Mbed TLS before 3.6.4 has a race condition in AESNI detection if certain compiler optimizations occur. | not reported in v5.5.1 |
| CVE-2026-25835 | mbed_tls 3.6.3 | high 7.7 | Mbed TLS before 3.6.6 and TF-PSA-Crypto before 1.1.0 misuse seeds in a Pseudo-Random Number Generator (PRNG). | not reported in v5.5.5 |
| CVE-2025-48965 | mbed_tls 3.6.3 | high 7.5 | Mbed TLS before 3.6.4 has a NULL pointer dereference because mbedtls_asn1_store_named_data can trigger conflicting data with val.p of NULL but val.len greater than zero. | not reported in v5.5.1 |
| CVE-2026-25833 | mbed_tls 3.6.3 | high 7.5 | Mbed TLS 3.5.0 to 3.6.5 fixed in 3.6.6 and 4.1.0 has a buffer overflow in the x509_inet_pton_ipv6() function | not reported in v5.5.5 |
| CVE-2026-34874 | mbed_tls 3.6.3 | high 7.5 | An issue was discovered in Mbed TLS through 3.6.5 and 4.x through 4.0.0. | not reported in v5.5.5 |
| CVE-2026-34876 | mbed_tls 3.6.3 | high 7.5 | An issue was discovered in Mbed TLS 3.x before 3.6.6. | not reported in v5.5.5 |
| CVE-2026-34871 | mbed_tls 3.6.3 | medium 6.7 | An issue was discovered in Mbed TLS before 3.6.6 and 4.x before 4.1.0 and TF-PSA-Crypto before 1.1.0. | not reported in v5.5.5 |
| CVE-2025-49601 | mbed_tls 3.6.3 | medium 6.5 | In MbedTLS 3.3.0 before 3.6.4, mbedtls_lms_import_public_key does not check that the input buffer is at least 4 bytes before reading a 32-bit field, allowing a possible out-of-bounds read on truncated input. | not reported in v5.5.1 |
| CVE-2026-25834 | mbed_tls 3.6.3 | medium 6.5 | Mbed TLS v3.3.0 up to 3.6.5 and 4.0.0 allows Algorithm Downgrade. | not reported in v5.5.5 |
| CVE-2025-54764 | mbed_tls 3.6.3 | medium 6.2 | Mbed TLS before 3.6.5 allows a local timing attack against certain RSA operations, and direct calls to mbedtls_mpi_mod_inv or mbedtls_mpi_gcd. | not reported in v5.5.2 |
| CVE-2025-59438 | mbed_tls 3.6.3 | medium 5.3 | Mbed TLS through 3.6.4 has an Observable Timing Discrepancy. | not reported in v5.5.2 |
| CVE-2025-66442 | mbed_tls 3.6.3 | medium 5.1 | In Mbed TLS through 4.0.0, there is a compiler-induced timing side channel (in RSA and CBC/ECB decryption) that only occurs with LLVM's select-optimize feature. | excluded from v5.5.5 |
| CVE-2025-49600 | mbed_tls 3.6.3 | medium 4.9 | In MbedTLS 3.3.0 before 3.6.4, mbedtls_lms_verify may accept invalid signatures if hash computation fails and internal errors go unchecked, enabling LMS (Leighton-Micali Signature) forgery in a fault scenario. | not reported in v5.5.1 |
| CVE-2025-52497 | mbed_tls 3.6.3 | medium 4.8 | Mbed TLS before 3.6.4 has a PEM parsing one-byte heap-based buffer underflow, in mbedtls_pem_read_buffer and two mbedtls_pk_parse functions, via untrusted PEM input. | not reported in v5.5.1 |
| CVE-2025-49087 | mbed_tls 3.6.3 | low 3.7 | In Mbed TLS 3.6.1 through 3.6.3 before 3.6.4, a timing discrepancy in block cipher padding removal allows an attacker to recover the plaintext when PKCS#7 padding mode is used. | not reported in v5.5.1 |
"In later releases" shows the first later 5.5 release in which Espressif's checker no longer reports the CVE. Check the release notes before relying on it for a fix.
Excluded by Espressif
These CVEs match a component's version in the NVD, but Espressif has excluded them for ESP-IDF, with the reason below. idf.py sbom-check leaves them out too.
- CVE-2023-52160 (wpa_supplicant 2.10): The relevant fix has been patched with https://github.com/espressif/esp-idf/commit/59a62f2af65945f92d475089f9ce66fce56cc737
- CVE-2024-28115 (freertos 10.5.1): Affects only ARMv7-M MPU ports, and ARMv8-M ports with Memory Protected Unit (MPU) support enabled
- CVE-2024-30949 (newlib 4.3.0): A vulnerability was discovered in the gettimeofday system call implementation within the RISC-V libgloss component of Newlib.
- CVE-2025-27840 (esp-idf 5.5.0): A security issue was reported concerning undocumented HCI commands in ESP32 Bluetooth controller.
- CVE-2026-77234 (freertos 10.5.1): A timer command submitted by an unprivileged task is executed by the timer service task as a caller-supplied function call.
- CVE-2026-77235 (freertos 10.5.1): Missing privilege verification in the secure context cleanup SVC handler, letting a Non-Secure task free another task's secure context (GHSA-55pf-q87x-c58c).
- CVE-2026-77236 (freertos 10.5.1): Missing minimum size validation in secure context allocation, writing the stack-overflow sentinel outside the allocated Secure-world buffer (GHSA-vq2f-9qj3-jj2m).
- CVE-2026-77237 (freertos 10.5.1): Missing queue-set type validation in xQueueAddToSet() leading to an out-of-bounds read in privileged kernel context.
Does it affect your firmware?
This list covers every component ESP-IDF v5.5 ships. Your application links only some of them: an app without Thread does not contain OpenThread, and one that does not parse JSON may not link cJSON. For the list that applies to your build, create its SBOM and check it:
pip install esp-idf-sbom idf.py sbom-create idf.py sbom-check
A vulnerability in a component you link is not always reachable: it may sit in a feature that is not enabled in your configuration. That judgement is yours to record; the Cyber Resilience Act asks you to handle each one and to keep track of it (what it asks).
This page is a snapshot from 2026-11-12; new vulnerabilities are published every week. Pinscope checks the SBOM of your own build against the NVD every day, with the same matching as Espressif's tool, and emails you when a new one appears in it. Free for one build, no card. The paid plans check every build, show which devices run an affected one, keep your decision on each CVE and ship the fix over the air (for the Cyber Resilience Act).
Components checked
SystemView 3.56, cjson 1.7.18, esp-idf 5.5.0, freertos 10.5.1, lwip 2.2.0, mbed_tls 3.6.3, micro-ecc 1.1, newlib 4.3.0, openthread 2023-07-06, protobuf-c 1.4.1, wpa_supplicant 2.10
Listed without an identifier the NVD uses, so not looked up: components/cmock/CMock v2.5.2-2-geeecc49ce8af, components/spiffs/spiffs 0.2-255-g0dbb3f71c5f6, components/unity/unity v2.6.0-RC1, Apache Mynewt Nimble 1.6.0, FatFs R0.15, FreeRTOS-Plus-POSIX 1.0.0, HTTP Parser 2.7.0, argtable3 3.2.2, openthread component 2023-07-06.
From the SBOM manifests in ESP-IDF v5.5 and its submodules, checked against the NVD with esp-idf-sbom manifest check and Espressif's list of excluded CVEs. The NVD changes daily; this page is regenerated from time to time. Espressif's own fixes and notes are in its security advisories. All ESP-IDF versions.
ESP-IDF and Espressif are trademarks of Espressif Systems; this page is not affiliated with or endorsed by Espressif.
More
- Remote access to an ESP32 without TLS: what it measured and what it costs
- Reaching an ESP32 web server from outside its network
- Updating ESP32 firmware over the internet, with rollback
- Guru Meditation Error: decoding the backtrace, and crashes from the field
- Remote logging: ESP_LOG without a serial cable
- Heap and stack monitoring in the field
- An ESP32 behind CGNAT, 4G or Starlink
- TLS memory usage on the ESP32, and how to reduce it
- Sharing an ESP32 sensor page with anyone, without port forwarding
- ArduinoOTA over the internet, with a rollback
- ESP32 remote access compared: port forwarding, ngrok, Cloudflare Tunnel, Tailscale
- esp_http_server slow? The 250 ms delay and the fix
- Before the first ESP32 ships: a field support checklist
- ESP32 exception decoder: a Guru Meditation backtrace to lines, in the browser