Which CVEs affect ESP-IDF 5.3.5?
| CVE | Severity | CVSS | Fixed from | Note |
|---|---|---|---|---|
| CVE-2026-45541 | high | 7.5 | not stated | per vulnerability databases |
| CVE-2026-45542 | high | 7.1 | not stated | per vulnerability databases |
| CVE-2026-45160 | medium | 6.5 | not stated | per vulnerability databases |
| CVE-2026-46532 | medium | 4.6 | not stated | per vulnerability databases |
What changed against ESP-IDF 5.3.4?
6 CVEs of 5.3.4 are no longer listed for 5.3.5: CVE-2025-66409, CVE-2025-68473, CVE-2025-68474, CVE-2026-25507, CVE-2026-25508, CVE-2026-25532.
4 CVEs are newly listed for 5.3.5: CVE-2026-45160, CVE-2026-45541, CVE-2026-45542, CVE-2026-46532.
What does the number mean for a device?
Counted are the CVEs public sources name for ESP-IDF version 5.3.5 (NVD). "Confirmed by the vendor" means the CVE record or advisory comes from the vendor itself and names this version as affected. Third-party records are counted but not marked as confirmed.
Whether a CVE is exploitable in a given device depends on which functions of the library the build contains and how they are configured. The list shows what is known for the version.
Questions
How many CVEs does ESP-IDF 5.3.5 have?
As of 13 Nov 2026, 4 CVEs are known for ESP-IDF 5.3.5, 0 critical and 2 high. 6.1, the newest listed version, lists none of them.
From which version are the CVEs of ESP-IDF 5.3.5 fixed?
No newer listed version is free of all 4 CVEs. The "Fixed from" column names the fix version per CVE for this release line where a source states one.
Sources
- [1]NVD