Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
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
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-11-04T19:04:16.828Z
Reserved: 2026-10-20T17:39:41.372Z
Link: CVE-2026-113783
No data.
Status : Received
Published: 2026-11-04T19:17:18.907
Modified: 2026-11-04T19:17:18.907
Link: CVE-2026-113783
No data.
OpenCVE Enrichment
Updated: 2026-11-04T20:30:17Z