Known vulnerabilities in ESP-IDF v4.4.7

Which CVEs affect the components ESP-IDF v4.4.7 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 v4.4.7: 4 critical, 10 high, 10 medium. Checked on 2026-11-12 with Espressif's esp-idf-sbom 1.4.0.

The newest release of this line is v4.4.8, with 23 known vulnerabilities reported (4 critical, 9 high, 10 medium).

Some components of this release cannot be checked (see below), so the real list may be longer.

Known vulnerabilities

CVEComponentSeverityWhat it isIn later 4.4 releases
CVE-2025-47917mbed_tls 2.28.7critical 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.reported in every later 4.4 release
CVE-2026-34877mbed_tls 2.28.7critical 9.8An issue was discovered in Mbed TLS versions from 2.19.0 up to 3.6.5, Mbed TLS 4.0.0.reported in every later 4.4 release
CVE-2025-66409esp-idf 4.4.7critical 9.1ESF-IDF is the Espressif Internet of Things (IOT) Development Framework.reported in every later 4.4 release
CVE-2026-34872mbed_tls 2.28.7critical 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.reported in every later 4.4 release
CVE-2025-55297esp-idf 4.4.7high 8.8ESF-IDF is the Espressif Internet of Things (IOT) Development Framework.reported in every later 4.4 release
CVE-2024-28960mbed_tls 2.28.7high 8.2An issue was discovered in Mbed TLS 2.18.0 through 2.28.x before 2.28.8 and 3.x before 3.6.0, and Mbed Crypto.not reported in v4.4.8
CVE-2024-28115freertos 10.4.3high 7.8FreeRTOS is a real-time operating system for microcontrollers.reported in every later 4.4 release
CVE-2025-52496mbed_tls 2.28.7high 7.8Mbed TLS before 3.6.4 has a race condition in AESNI detection if certain compiler optimizations occur.reported in every later 4.4 release
CVE-2026-25835mbed_tls 2.28.7high 7.7Mbed TLS before 3.6.6 and TF-PSA-Crypto before 1.1.0 misuse seeds in a Pseudo-Random Number Generator (PRNG).reported in every later 4.4 release
CVE-2024-31755cjson 1.7.17high 7.6cJSON v1.7.17 was discovered to contain a segmentation violation, which can trigger through the second parameter of function cJSON_SetValuestring at cJSON.c.reported in every later 4.4 release
CVE-2021-43666mbed_tls 2.28.7high 7.5A Denial of Service vulnerability exists in mbed TLS 3.0.0 and earlier in the mbedtls_pkcs12_derivation function when an input password's length is 0.reported in every later 4.4 release
CVE-2021-45451mbed_tls 2.28.7high 7.5In Mbed TLS before 3.1.0, psa_aead_generate_nonce allows policy bypass or oracle-based decryption when the output buffer is at memory locations accessible to an untrusted application.reported in every later 4.4 release
CVE-2023-52353mbed_tls 2.28.7high 7.5An issue was discovered in Mbed TLS through 3.5.1.reported in every later 4.4 release
CVE-2025-48965mbed_tls 2.28.7high 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.reported in every later 4.4 release
CVE-2026-34871mbed_tls 2.28.7medium 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.reported in every later 4.4 release
CVE-2025-54764mbed_tls 2.28.7medium 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.reported in every later 4.4 release
CVE-2023-53154cjson 1.7.17medium 5.5parse_string in cJSON before 1.7.18 has a heap-based buffer over-read via {"1":1, with no trailing newline if cJSON_ParseWithLength is called.reported in every later 4.4 release
CVE-2025-27809mbed_tls 2.28.7medium 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.reported in every later 4.4 release
CVE-2025-59438mbed_tls 2.28.7medium 5.3Mbed TLS through 3.6.4 has an Observable Timing Discrepancy.reported in every later 4.4 release
CVE-2024-45157mbed_tls 2.28.7medium 5.1An issue was discovered in Mbed TLS before 2.28.9 and 3.x before 3.6.1, in which the user-selected algorithm is not used.reported in every later 4.4 release
CVE-2025-66442mbed_tls 2.28.7medium 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.reported in every later 4.4 release
CVE-2025-27810mbed_tls 2.28.7medium 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…reported in every later 4.4 release
CVE-2025-52497mbed_tls 2.28.7medium 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.reported in every later 4.4 release
CVE-2021-36647mbed_tls 2.28.7medium 4.7Use of a Broken or Risky Cryptographic Algorithm in the function mbedtls_mpi_exp_mod() in lignum.c in Mbed TLS Mbed TLS all versions before 3.0.0, 2.27.0 or 2.16.11 allows attackers with access to precise enough timing…reported in every later 4.4 release

"In later releases" shows the first later 4.4 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 v4.4.7 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.17, esp-idf 4.4.7, freertos 10.4.3, lwip 2.1.2, mbed_tls 2.28.7, micro-ecc 1.1, protobuf-c 1.4.1

Not checked in this release: newlib, openthread, wpa_supplicant. ESP-IDF v4.4.7 has no SBOM manifest for them (other releases do), so Espressif's checker cannot look them up. Their vulnerabilities are not in the list above; check those components yourself.

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.4.3-51-g7d2bf62b7e6a, FatFs R0.13c.

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