CVE-2026-113783
ESP-IDF: Stack-based memory corruption in lwIP DNS/SNTP handling for multi-IP DNS responses
ESP-IDF is the Espressif Internet of Things (IOT) Development Framework. From 5.2.3 until 5.3.7, 5.4.5, 5.5.6, and 6.0.3, the lwIP DNS resolver's cached-lookup path in dns_lookup() in dns.c copies every cached address into a caller-provided single ip_addr_t output buffer without a length parameter or bounds check. When CONFIG_LWIP_DNS_MAX_HOST_IP is greater than 1 and a cached hostname has multiple A or AAAA records, a subsequent lookup through dns_gethostbyname() or dns_gethostbyname_addrtype() writes beyond the single-element buffer into adjacent stack memory. A network-positioned attacker who influences DNS responses can cause a reboot through stack-canary corruption or, without stack protection, overwrite stack variables with attacker-controlled address bytes and potentially redirect control flow. This issue is fixed in versions 5.5.6 and 6.0.3 and is scheduled to be fixed in versions 5.3.7 and 5.4.5. No fixed release is available for the end-of-life 5.2 line.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| esp-idf espressif |
>= 5.2.3, <= 5.2.8 (affected) >= 5.3.2, < 5.3.7 (affected) >= 5.4.0, < 5.4.5 (affected) >= 5.5.0, < 5.5.6 (affected) >= 6.0.0, < 6.0.3 (affected) |
CNA: GitHub_M |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 7.4 high |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H | CNA: GitHub_M |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://github.com/espressif/esp-idf/security/advisories/GHSA-ch63-jxm5-vmvfCNA: GitHub_M · x_refsource_CONFIRM
- https://github.com/espressif/esp-idf/commit/75f2ff7e0c2d19e113293ec122b701c83d2f6665CNA: GitHub_M · x_refsource_MISC
- https://github.com/espressif/esp-idf/commit/7ab85eb4dc7d7695960d940badcd62592c365056CNA: GitHub_M · x_refsource_MISC
- https://github.com/espressif/esp-idf/commit/882843dbf838b0c02e09d46bb6283bda73496b8cCNA: GitHub_M · x_refsource_MISC
- https://github.com/espressif/esp-idf/commit/98e6e7a08fca391563651a1e751cc45a3b27d18bCNA: GitHub_M · x_refsource_MISC
- https://github.com/espressif/esp-idf/commit/af7543d00a4d7b489e010a70b59fd3d8022a40f4CNA: GitHub_M · x_refsource_MISC
- https://github.com/espressif/esp-idf/commit/defaa2f559470acfee5e2e5ea80a79b73424d483CNA: GitHub_M · x_refsource_MISC
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.