CVE-2026-45541 json
ESF-IDF: Remote Null Pointer Dereference in WebSocket Server
published 4mo ago modified 3mo ago also EUVD-2026-35914
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- public exploits
- 0
- none known
Summary
ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. In versions 5.2.6, 5.3.5, 5.4.4, 5.5.4, and 6.0, a NULL-pointer dereference exists in the WebSocket subprotocol-negotiation path of the esp_http_server component. While parsing the client-supplied Sec-WebSocket-Protocol request header during the WebSocket handshake, the tokenisation result is dereferenced without a NULL check, so a malformed header value can crash the server before any application-level authentication runs. This issue has been patched in versions 5.2.7, 5.3.6, 5.4.5, 5.5.5, and 6.0.1.
Patch / fix
- espressif esp-idf 5.2.7, 5.3.6, 5.4.5, 5.5.5, 6.0.1
- github.com/espressif/esp-idf@00a2f7f commit
- github.com/espressif/esp-idf@0dc4ee7 commit
- github.com/espressif/esp-idf@37508ab commit
- github.com/espressif/esp-idf@9fc0ca1 commit
- github.com/espressif/esp-idf@dc46dc5 commit
- github.com/espressif/esp-idf@f88a47e commit
- github.com/espressif/esp-idf/security/advisories/GHSA-3j8v-xgrq-5vg8 advisory
Is CVE-2026-45541 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 4mo ago
Exploit prediction
0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- espressif esp-idf
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
References
-
github.com
/espressif/esp-idf/commit/00a2f7fbbbd8fe6d04729022e1d5c9a49435bfe8
patch
-
github.com
/espressif/esp-idf/commit/0dc4ee7537f3b12350f5966cecacd59bba840ec6
patch
-
github.com
/espressif/esp-idf/commit/37508ab91124ef426a7396d30f79eba1162700c7
patch
-
github.com
/espressif/esp-idf/commit/9fc0ca13b3b85b98d32b98cd9dc8ff9d82642b7b
patch
-
github.com
/espressif/esp-idf/commit/dc46dc51359749e50617eb70d6f9ae298adc4fff
patch
-
github.com
/espressif/esp-idf/commit/f88a47e4f37fb11ae4b0908cd5c80059d83198c6
patch
-
github.com
/espressif/esp-idf/security/advisories/GHSA-3j8v-xgrq-5vg8
mitigation, patch, vendor-advisory
Sources
- CVE List CVE-2026-45541
- NVD CVE-2026-45541
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.