ESP-IDF: Stack-Based Out-of-Bounds Write in Thread Border Router ND6 Option Parsing
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.2.8, 5.3.6, 5.4.5, 5.5.5, 6.0.3
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Firmware built with CONFIG_OPENTHREAD_BORDER_ROUTER=y ESP-IDF releases v5.2 through v5.2.7, v5.3 through v5.3.5, v5.4 through v5.4.4, v5.5 through v5.5.4, and v6.0 through v6.0.2
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
CVE-2026-113782 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects esp-idf; fixed in 5.2.8, 5.3.6, 5.4.5 and 2 more.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 5.2.8, 5.3.6, 5.4.5, 5.5.5, 6.0.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
ESP-IDF's OpenThread Border Router feature contains a stack-based out-of-bounds write in its Neighbor Discovery packet handling, which an attacker on an adjacent network can trigger without logging in or any user action by sending a crafted ICMPv6 Router Advertisement. A successful attack can crash or reboot the device or corrupt adjacent stack memory.
Read the original 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.
What to do
Check whether your setup matches what the bug needs.
Firmware built with CONFIG_OPENTHREAD_BORDER_ROUTER=y ESP-IDF releases v5.2 through v5.2.7, v5.3 through v5.3.5, v5.4 through v5.4.4, v5.5 through v5.5.4, and v6.0 through v6.0.2Upgrade to a fixed version: 5.2.8, 5.3.6, 5.4.5, 5.5.5, 6.0.3.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- espressif esp-idf
From 5.2.0 · fixed in 5.2.8; From 5.3.0 · fixed in 5.3.6; From 5.4.0 · fixed in 5.4.5; From 5.5.0 · fixed in 5.5.5; From 6.0.0 · fixed in 6.0.3
Evidence 7
- Advisory
- Repository
- Repository
- Repository
- Repository
Show all 7 sourcesShow fewer sources
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-113782
Is CVE-2026-113782 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A crafted ND6 option in a Thread Border Router parser writes past the end of a stack buffer. The result can be a device crash and reboot, or corruption of nearby stack memory.Source: github.com
Which versions are affected by CVE-2026-113782?
esp-idf: from 5.2.0 before 5.2.8; from 5.3.0 before 5.3.6; from 5.4.0 before 5.4.5; from 5.5.0 before 5.5.5; from 6.0.0 before 6.0.3.Source: cve.now feed data
Am I affected, and how do I check?
Only firmware built with CONFIG_OPENTHREAD_BORDER_ROUTER=y is affected, on ESP-IDF releases v5.2 through v5.2.7, v5.3 through v5.3.5, v5.4 through v5.4.4, v5.5 through v5.5.4, and v6.0 through v6.0.2. To check a build, look for CONFIG_OPENTHREAD_BORDER_ROUTER in the project's sdkconfig and confirm the ESP-IDF version in use.Source: github.com
How do I fix CVE-2026-113782?
Upgrade to a fixed release: 5.2.8, 5.3.6, 5.4.5, 5.5.5, or 6.0.3, matching your release line.Source: github.com