Known vulnerabilities in ESP-IDF v5.3.3

Which CVEs affect the components ESP-IDF v5.3.3 ships, such as mbed TLS, lwIP and cJSON, according to Espressif's own checker, and in which later release they are no longer reported.

24 known vulnerabilities reported for the components of ESP-IDF v5.3.3: 7 critical, 6 high, 10 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.3.6, with 6 known vulnerabilities reported (4 high, 2 medium).

Known vulnerabilities

CVEComponentSeverityWhat it isIn later 5.3 releases
CVE-2025-47917mbed_tls 3.6.2critical 9.8Mbed 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.3.4
CVE-2025-52471esp-idf 5.3.3critical 9.8ESF-IDF is the Espressif Internet of Things (IOT) Development Framework.not reported in v5.3.4
CVE-2026-34875mbed_tls 3.6.2critical 9.8An issue was discovered in Mbed TLS through 3.6.5 and TF-PSA-Crypto 1.0.0.not reported in v5.3.6
CVE-2026-34877mbed_tls 3.6.2critical 9.8An 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.3.6
CVE-2025-66409esp-idf 5.3.3critical 9.1ESF-IDF is the Espressif Internet of Things (IOT) Development Framework.not reported in v5.3.5
CVE-2026-34872mbed_tls 3.6.2critical 9.1An 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.3.6
CVE-2026-34873mbed_tls 3.6.2critical 9.1An issue was discovered in Mbed TLS 3.5.0 through 4.0.0.not reported in v5.3.6
CVE-2025-52496mbed_tls 3.6.2high 7.8Mbed TLS before 3.6.4 has a race condition in AESNI detection if certain compiler optimizations occur.not reported in v5.3.4
CVE-2026-25835mbed_tls 3.6.2high 7.7Mbed 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.3.6
CVE-2025-48965mbed_tls 3.6.2high 7.5Mbed 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.3.4
CVE-2026-25833mbed_tls 3.6.2high 7.5Mbed 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() functionnot reported in v5.3.6
CVE-2026-34874mbed_tls 3.6.2high 7.5An issue was discovered in Mbed TLS through 3.6.5 and 4.x through 4.0.0.not reported in v5.3.6
CVE-2026-34876mbed_tls 3.6.2high 7.5An issue was discovered in Mbed TLS 3.x before 3.6.6.not reported in v5.3.6
CVE-2026-34871mbed_tls 3.6.2medium 6.7An 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.3.6
CVE-2025-49601mbed_tls 3.6.2medium 6.5In 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.3.4
CVE-2026-25834mbed_tls 3.6.2medium 6.5Mbed TLS v3.3.0 up to 3.6.5 and 4.0.0 allows Algorithm Downgrade.not reported in v5.3.6
CVE-2025-54764mbed_tls 3.6.2medium 6.2Mbed 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.3.5
CVE-2025-27809mbed_tls 3.6.2medium 5.4Mbed TLS before 2.28.10 and 3.x before 3.6.3, on the client side, accepts servers that have trusted certificates for arbitrary hostnames unless the TLS client application calls mbedtls_ssl_set_hostname.not reported in v5.3.4
CVE-2025-59438mbed_tls 3.6.2medium 5.3Mbed TLS through 3.6.4 has an Observable Timing Discrepancy.not reported in v5.3.5
CVE-2025-66442mbed_tls 3.6.2medium 5.1In 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.3.6
CVE-2025-49600mbed_tls 3.6.2medium 4.9In 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.3.4
CVE-2025-27810mbed_tls 3.6.2medium 4.8Mbed TLS before 2.28.10 and 3.x before 3.6.3, in some cases of failed memory allocation or hardware errors, uses uninitialized stack memory to compose the TLS Finished message, potentially leading to authentication…not reported in v5.3.4
CVE-2025-52497mbed_tls 3.6.2medium 4.8Mbed 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.3.4
CVE-2025-49087mbed_tls 3.6.2low 3.7In 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.3.4

"In later releases" shows the first later 5.3 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.

Does it affect your firmware?

This list covers every component ESP-IDF v5.3.3 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).

Watch your firmware, free See the live demo

Components checked

cjson 1.7.18, esp-idf 5.3.3, freertos 10.5.1, lwip 2.1.3, mbed_tls 3.6.2, 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, HTTP Parser 2.7.0, argtable3 3.2.2, openthread component 2023-07-06.

From the SBOM manifests in ESP-IDF v5.3.3 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