Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-25532: CWE-191: Integer Underflow (Wrap or Wraparound) in espressif esp-idf

0
Medium
VulnerabilityCVE-2026-25532cvecve-2026-25532cwe-191
Published: Wed Feb 04 2026 (02/04/2026, 17:58:08 UTC)
Source: CVE Database V5
Vendor/Project: espressif
Product: esp-idf

Description

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.

AI-Powered Analysis

AILast updated: 02/04/2026, 18:29:42 UTC

Technical Analysis

The vulnerability CVE-2026-25532 affects the Espressif Internet of Things Development Framework (esp-idf), specifically in versions 5.1.6, 5.2.6, 5.3.4, 5.4.3, and 5.5.2. It resides in the Wi-Fi Protected Setup (WPS) Enrollee implementation, where the processing of EAP-Expanded (WSC) messages involves calculating a fragment length (frag_len) by subtracting header sizes from the total packet length. An attacker can send malformed EAP-WSC packets with truncated payloads that omit expected fields such as the 2-byte Message Length when the WPS_MSG_FLAG_LEN flag is set. This causes frag_len to become negative. Since frag_len is then implicitly cast to an unsigned size_t type when passed to the wpabuf_put_data() function, it results in a very large value, leading to buffer overflows or memory corruption. This integer underflow (CWE-191) can cause denial of service by crashing the device or potentially enable further exploitation depending on the memory corruption impact. The vulnerability requires an attacker to send crafted packets over the network to a vulnerable device, and user interaction is limited to the device processing these packets. Espressif has released patches in versions 5.1.7, 5.2.7, 5.3.5, 5.4.4, and 5.5.3 to address this issue. No public exploits have been reported yet, but the medium CVSS score (6.3) reflects the moderate risk due to the network attack vector and potential for availability impact.

Potential Impact

For European organizations deploying IoT devices based on esp-idf, this vulnerability could lead to denial of service conditions, causing device outages or instability in critical infrastructure or consumer environments. Given the widespread use of Espressif chips in smart home devices, industrial sensors, and other IoT applications, disruption could affect operational continuity and service availability. While the vulnerability does not directly impact confidentiality or integrity, denial of service in IoT environments can have cascading effects, especially in sectors like manufacturing, energy, and smart city deployments prevalent in Europe. The requirement for network access means that attackers could exploit this remotely if devices are exposed or reachable through internal networks. The absence of known exploits reduces immediate risk, but the medium severity and ease of triggering the flaw through malformed packets necessitate prompt remediation to prevent potential attacks.

Mitigation Recommendations

European organizations should immediately update esp-idf to the patched versions 5.1.7, 5.2.7, 5.3.5, 5.4.4, or 5.5.3 depending on their current version. For devices already deployed and difficult to update, network segmentation and strict firewall rules should be applied to limit exposure of IoT devices to untrusted networks. Monitoring network traffic for anomalous or malformed EAP-WSC packets can help detect attempted exploitation. Additionally, disabling WPS functionality on devices where it is not required can reduce the attack surface. Vendors and integrators should verify firmware versions and ensure secure update mechanisms are in place. Finally, organizations should conduct security assessments of their IoT deployments to identify vulnerable devices and prioritize patching or mitigation accordingly.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-02T19:59:47.373Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69838cacf9fa50a62fa093a1

Added to database: 2/4/2026, 6:15:08 PM

Last enriched: 2/4/2026, 6:29:42 PM

Last updated: 2/7/2026, 12:00:55 AM

Views: 22

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats