espressif esp-idf up to 6.0 null pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.70- |
Summary
A vulnerability classified as problematic has been found in espressif esp-idf 5.2.6/5.3.5/5.4.4/5.5.4/6.0. Affected by this issue is some unknown functionality. The manipulation leads to null pointer dereference. This vulnerability is traded as CVE-2026-45541. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in espressif esp-idf 5.2.6/5.3.5/5.4.4/5.5.4/6.0. This issue affects some unknown processing. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. Impacted is availability. The summary by CVE is:
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.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-45541 since 05/12/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 5.2.6, 5.2.7, 5.3.5, 5.3.6, 5.4.4, 5.4.5, 5.5.4, 5.5.5, 6.0 or 6.0.1 eliminates this vulnerability. Applying the patch 00a2f7fbbbd8fe6d04729022e1d5c9a49435bfe8 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: esp-idf 5.2.6/5.2.7/5.3.5/5.3.6/5.4.4/5.4.5/5.5.4/5.5.5/6.0/6.0.1
Patch: 00a2f7fbbbd8fe6d04729022e1d5c9a49435bfe8
Timeline
05/12/2026 CVE reserved06/10/2026 Advisory disclosed
06/10/2026 VulDB entry created
06/10/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-3j8v-xgrq-5vg8
Status: Confirmed
CVE: CVE-2026-45541 (🔒)
GCVE (CVE): GCVE-0-2026-45541
GCVE (VulDB): GCVE-100-370019
Entry
Created: 06/10/2026 06:26Changes: 06/10/2026 06:26 (66)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.