Espressif ESP-IDF 5.1.6/5.2.6/5.3.4/5.4.3/5.5.2 wpabuf_put_data frag_len integer underflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.09 |
Summary
A vulnerability, which was classified as problematic, has been found in Espressif ESP-IDF 5.1.6/5.2.6/5.3.4/5.4.3/5.5.2. Affected is the function wpabuf_put_data. The manipulation of the argument frag_len leads to integer underflow.
This vulnerability is uniquely identified as CVE-2026-25532. The attack can only be initiated within the local network. No exploit exists.
It is advisable to upgrade the affected component.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability, which was classified as problematic, has been found in Espressif ESP-IDF 5.1.6/5.2.6/5.3.4/5.4.3/5.5.2. This issue affects the function wpabuf_put_data. The manipulation of the argument frag_len with an unknown input leads to a integer underflow vulnerability. Using CWE to declare the problem leads to CWE-191. The product subtracts one value from another, such that the result is less than the minimum allowable integer value, which produces a value that is not equal to the correct result. Impacted is integrity, and availability. The summary by CVE is:
ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. In versions 5.5.2, 5.4.3, 5.3.4, 5.2.6, and 5.1.6, a vulnerability exists in the WPS (Wi-Fi Protected Setup) Enrollee implementation where malformed EAP-WSC packets with truncated payloads can cause integer underflow during fragment length calculation. When processing EAP-Expanded (WSC) messages, the code computes frag_len by subtracting header sizes from the total packet length. If an attacker sends a packet where the EAP Length field covers only the header and flags but omits the expected payload (such as the 2-byte Message Length field when WPS_MSG_FLAG_LEN is set), frag_len becomes negative. This negative value is then implicitly cast to size_t when passed to wpabuf_put_data(), resulting in a very large unsigned value. This issue has been patched in versions 5.5.3, 5.4.4, 5.3.5, 5.2.7, and 5.1.7.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-25532 since 02/02/2026. The exploitation is known to be easy. The attack can only be done within the local network. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 5.1.6, 5.1.7, 5.2.6, 5.2.7, 5.3.4, 5.3.5, 5.4.3, 5.4.4, 5.5.2 or 5.5.3 eliminates this vulnerability. Applying the patch 60f992a26de17bb5406f2149a2f8282dd7ad1c59 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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.3
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: Integer underflowCWE: CWE-191 / CWE-189
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
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.1.6/5.1.7/5.2.6/5.2.7/5.3.4/5.3.5/5.4.3/5.4.4/5.5.2/5.5.3
Patch: 60f992a26de17bb5406f2149a2f8282dd7ad1c59
Timeline
02/02/2026 CVE reserved02/04/2026 Advisory disclosed
02/04/2026 VulDB entry created
02/04/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-m2h2-683f-9mw7
Status: Confirmed
CVE: CVE-2026-25532 (🔒)
GCVE (CVE): GCVE-0-2026-25532
GCVE (VulDB): GCVE-100-344387
Entry
Created: 02/04/2026 08:01 PMChanges: 02/04/2026 08:01 PM (67)
Complete: 🔍
Cache ID: 18:D71:40
No comments yet. Languages: en.
Please log in to comment.