Known vulnerabilities in ESP-IDF v6.0.2
Which CVEs affect the components ESP-IDF v6.0.2 ships, such as mbed TLS, lwIP and cJSON, according to Espressif's own checker, and in which later release they are no longer reported.
0 known vulnerabilities reported for the components of ESP-IDF v6.0.2: none. Checked on 2026-11-12 with Espressif's esp-idf-sbom 1.4.0.
The newest release of this line is v6.0.3, with 0 known vulnerabilities reported (none).
Known vulnerabilities
Espressif's checker reports no known vulnerability affecting the components of this release.
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-2025-27840 (esp-idf 6.0.2): 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 v6.0.2 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
esp-idf 6.0.2, freertos 10.5.1, lwip 2.2.0, mbed_tls 4.1.0, micro-ecc 1.1, openthread 2023-07-06, protobuf-c 1.4.1, tf-psa-crypto 1.1.0, 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-265-gad902ca, 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, esp_libc, openthread component 2023-07-06.
From the SBOM manifests in ESP-IDF v6.0.2 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