Known vulnerabilities in each ESP-IDF version
Which ESP-IDF releases ship components with known vulnerabilities, how serious they are, and which release of each line has the fewest. From Espressif's own checker, for every release since the SBOM manifests were added.
For each ESP-IDF release: the known vulnerabilities in the components it ships (mbed TLS, lwIP, cJSON, FreeRTOS, wpa_supplicant, OpenThread, ESP-IDF itself and the rest), as Espressif's own esp-idf-sbom 1.4.0 reports them against the NVD. Checked on 2026-11-12.
Using the Arduino core? Which ESP-IDF each Arduino ESP32 core release is built on, with its known vulnerabilities.
Older releases (before v4.4.6, v5.0.4 and v5.1.1) do not carry the SBOM manifests the tool reads, so they cannot be checked the same way and are not listed; the newest release of their line is. Early releases with manifests do not have them for every component yet: Checked shows how many of the release's components that can be looked up in the NVD were looked up, and each release's page names the ones that were not. A low total with few components checked is not a clean bill of health.
ESP-IDF 6.1
| Release | Critical | High | Medium | Low | Total | Checked |
| v6.1 newest | | | | | 0 | 9 of 9 |
ESP-IDF 6.0
ESP-IDF 5.5
ESP-IDF 5.4
| Release | Critical | High | Medium | Low | Total | Checked |
| v5.4.4 newest | 4 | 9 | 6 | | 19 | 10 of 10 |
| v5.4.3 | 5 | 10 | 8 | | 23 | 10 of 10 |
| v5.4.2 | 6 | 6 | 8 | 1 | 21 | 10 of 10 |
| v5.4.1 | 7 | 6 | 10 | 1 | 24 | 10 of 10 |
| v5.4 | 6 | 7 | 10 | 1 | 24 | 10 of 10 |
ESP-IDF 5.3
ESP-IDF 5.2
ESP-IDF 5.1
ESP-IDF 5.0
ESP-IDF 4.4
| Release | Critical | High | Medium | Low | Total | Checked |
| v4.4.8 newest | 4 | 9 | 10 | | 23 | 7 of 10 |
| v4.4.7 | 4 | 10 | 10 | | 24 | 7 of 10 |
| v4.4.6 | 4 | 11 | 12 | 1 | 28 | 5 of 10 |
How to read it
These are the components a release ships, not the ones your application links. For your own build, idf.py sbom-create and idf.py sbom-check give the exact list, and Pinscope keeps checking it every day for every build you ship, with the devices that run it (for the Cyber Resilience Act).
CVEs that Espressif has excluded for ESP-IDF are not counted; each release's page lists them with Espressif's reasons. Severity is the NVD's CVSS base severity. For Espressif's own fixes and notes, see its security advisories. Found a mistake? Write to hello@pinscope.dev.
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