<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VulnFeed.org: espressif esp-idf</title><link>https://vulnfeed.org/</link><description>Every disclosure, as it lands. Critical-only feed available.</description><language>en</language><atom:link href="https://vulnfeed.org/feed/product/espressif-esp-idf.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-113780: ESF-IDF: Unvalidated Stack Pointer at the ESP-TEE Privilege-Switch Boundary</title><link>https://vulnfeed.org/cve/CVE-2026-113780/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-113780/</guid><pubDate>Wed, 04 Nov 2026 19:17:18 +0000</pubDate><description>ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. From 5.5.5 until 5.5.6, 6.0.4, and 6.1.1, the esp_tee trap entry in esp_tee_vectors_plic.S and esp_tee_vectors_clic.S saves a caller-controlled register frame through the REE-supplied stack pointer before switching to the trusted TEE stack or validating the pointer. A local unprivileged REE application can direct this machine-mode write into TEE-exclusive memory on ESP32-C5, ESP32-C6, ESP32-C61, and ESP32-H2 devices, breaking the REE/TEE isolation boundary and potentially corrupting TEE control-flow data for code execution, denial of service, or system crashes. Both secure-service ecall and interrupt entry paths contain the vulnerable ordering. This issue is fixed in version 5.5.6 and is scheduled to be fixed in versions 6.0.4 and 6.1.1.</description></item><item><title>CVE-2026-113783: ESP-IDF: Stack-based memory corruption in lwIP DNS/SNTP handling for multi-IP DNS responses</title><link>https://vulnfeed.org/cve/CVE-2026-113783/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-113783/</guid><pubDate>Wed, 04 Nov 2026 19:17:18 +0000</pubDate><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&apos;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.</description></item><item><title>CVE-2026-113782: ESP-IDF: Stack-Based Out-of-Bounds Write in Thread Border Router ND6 Option Parsing</title><link>https://vulnfeed.org/cve/CVE-2026-113782/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-113782/</guid><pubDate>Wed, 04 Nov 2026 18:59:12 +0000</pubDate><description>ESP-IDF is the Espressif Internet of Things (IOT) Development Framework. From 5.2.0 until 5.2.8, 5.3.6, 5.4.5, 5.5.5, and 6.0.3, the OpenThread Border Router Neighbor Discovery packet handler trusts an attacker-controlled ICMPv6 option length while copying into a fixed stack buffer. A host on the same infrastructure link as the Border Router can send a crafted ICMPv6 Router Advertisement to its infrastructure interface whose oversized length causes an out-of-bounds write into adjacent stack memory. Firmware is affected only when CONFIG_OPENTHREAD_BORDER_ROUTER=y; Thread end devices, routers, and RCP firmware without the Border Router feature are unaffected. Exploitation requires no authentication or user interaction and can crash or reboot the device or corrupt adjacent stack state. This issue is fixed in versions 5.2.8, 5.3.6, 5.5.5, and 6.0.3 and is scheduled to be fixed in version 5.4.5.</description></item></channel></rss>
