Description
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.
Published: 2026-11-04
Score: 7.4 High
EPSS: n/a
KEV: No
Impact: Stack corruption enabling remote code execution via crafted DNS responses
Action: Patch immediately
AI Analysis

Impact

An unchecked copy in the lwIP DNS resolver copies every cached IP address into a caller‑provided single ip_addr_t buffer, causing a stack overflow when a hostname has more than one A or AAAA record and the CONFIG_LWIP_DNS_MAX_HOST_IP setting is greater than one. The overflow corrupts the stack canary or adjacent stack variables, which an attacker can use to reboot the device or hijack execution. The weakness is classified as CWE‑121.

Affected Systems

Espressif ESP‑IDF releases 5.2.3 through 5.3.7, 5.4.5, 5.5.6, and 6.0.3 contain the vulnerable code. Versions 5.5.6 and 6.0.3 already include the fix, and the fix is scheduled for 5.3.7 and 5.4.5. The end‑of‑life 5.2 series has no patched release.

Risk and Exploitability

The CVSS score of 7.4 indicates a high severity vulnerability. The EPSS score is not available and the issue is not listed in CISA KEV, but a network‑positioned attacker controlling DNS responses can trigger the overflow. Because the exploit requires delivering a crafted DNS response that contains multiple IPs for a cached hostname, it is an attack that can be carried out from the local network or by compromising the DNS server the device uses. The potential impact of crashing the device or hijacking control flow makes the risk significant for exposed devices.

Generated by OpenCVE AI on November 4, 2026 at 20:21 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the ESP‑IDF source to version 5.5.6, 6.0.3, or a later fixed release; the patch for 5.3.7 and 5.4.5 is scheduled and should be applied as soon as available.
  • If the device is running ESP‑IDF 5.2.x or another unsupported version, disable or replace the lwIP DNS resolver, or use a static IP configuration to eliminate DNS queries.
  • Configure the build to set CONFIG_LWIP_DNS_MAX_HOST_IP to 1 or disable it entirely, reducing the buffer overflow risk by ensuring only a single IP address can be cached per hostname.

Generated by OpenCVE AI on November 4, 2026 at 20:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 04 Nov 2026 21:00:00 +0000

Type Values Removed Values Added
First Time appeared Espressif
Espressif esp-idf
Vendors & Products Espressif
Espressif esp-idf

Wed, 04 Nov 2026 19:15:00 +0000

Type Values Removed Values Added
Description 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.
Title ESP-IDF: Stack-based memory corruption in lwIP DNS/SNTP handling for multi-IP DNS responses
Weaknesses CWE-121
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H'}


Subscriptions

Espressif Esp-idf
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-11-04T19:04:16.828Z

Reserved: 2026-10-20T17:39:41.372Z

Link: CVE-2026-113783

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-04T19:17:18.907

Modified: 2026-11-04T19:17:18.907

Link: CVE-2026-113783

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-04T20:45:07Z

Weaknesses
  • CWE-121

    Stack-based Buffer Overflow