Known vulnerabilities in ESP-IDF v5.2.7

Which CVEs affect the components ESP-IDF v5.2.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.

5 known vulnerabilities reported for the components of ESP-IDF v5.2.7: 3 high, 2 medium. Checked on 2026-11-12 with Espressif's esp-idf-sbom 1.4.0.

The newest release of this line is v5.2.8, with 4 known vulnerabilities reported (3 high, 1 medium).

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

Known vulnerabilities

CVEComponentSeverityWhat it isIn later 5.2 releases
CVE-2026-67215cjson 1.7.19high 8.7cJSON through 1.7.19 is vulnerable to uncontrolled recursion leading to stack exhaustion when an untrusted RFC 6902 JSON Patch is applied via cJSONUtils_ApplyPatches() or cJSONUtils_ApplyPatchesCaseSensitive().reported in every later 5.2 release
CVE-2026-16554cjson 1.7.19high 7.8cJSON library is vulnerable to an integer overflow in the print_string_ptr() function in cJSON.c on 32-bit platforms.reported in every later 5.2 release
CVE-2026-67216cjson 1.7.19high 7.5cJSON through 1.7.19 contains an inefficient algorithmic complexity flaw in cJSON_Compare().reported in every later 5.2 release
CVE-2026-67217cjson 1.7.19medium 6.9cJSON through 1.7.19 applies RFC 6902 JSON Patch operations non-atomically in apply_patch() in cJSON_Utils.c.reported in every later 5.2 release
CVE-2026-45160esp-idf 5.2.7medium 6.5ESF-IDF is the Espressif Internet of Things (IOT) Development Framework.not reported in v5.2.8

"In later releases" shows the first later 5.2 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.2.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.19, esp-idf 5.2.7, freertos 10.5.1, lwip 2.1.3, mbed_tls 3.6.6, micro-ecc 1.1, newlib 4.3.0, protobuf-c 1.4.1

Not checked in this release: openthread, wpa_supplicant. ESP-IDF v5.2.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, Apache Mynewt Nimble 1.5.0, FatFs R0.15, HTTP Parser 2.7.0, argtable3 3.2.2.

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