Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-85079 Overview
CVE-2026-85079 is an out-of-bounds write vulnerability in Silicon Labs EmberZNet versions 9.1.1 and earlier. The flaw resides in the handling of Simple_Desc_req responses within the Zigbee stack. A malformed response can corrupt memory and potentially lead to remote code execution on the affected device. Exploitation requires that the attacker-controlled device has already joined the Zigbee network. The attacker must also wait for a legitimate Simple_Desc_req to be issued before injecting the malformed response. The vulnerability is categorized under [CWE-121] Stack-based Buffer Overflow.
Critical Impact
A joined Zigbee device can trigger an out-of-bounds write on peers processing its Simple_Desc_req response, potentially leading to remote code execution over the adjacent network.
Affected Products
- Silicon Labs EmberZNet 9.1.1
- Silicon Labs EmberZNet prior to 9.1.1
- Zigbee devices built on the EmberZNet protocol stack
Discovery Timeline
- 2026-10-22 - CVE-2026-85079 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-85079
Vulnerability Analysis
The vulnerability affects how the EmberZNet stack parses Zigbee Device Object (ZDO) Simple_Desc_req responses. When a response is malformed, the stack writes data beyond the bounds of an allocated buffer. This out-of-bounds write condition, classified as [CWE-121], can corrupt adjacent memory structures on the stack. An attacker who controls a joined Zigbee device can craft a response that overwrites return addresses or control data. Successful exploitation may redirect execution flow and achieve code execution on the receiving device. The attack requires adjacent network access and operates within the Zigbee radio range of the target.
Root Cause
The root cause is insufficient bounds checking during the parsing of fields contained in a Simple_Desc_req response. The EmberZNet stack trusts length or descriptor fields supplied by the responding device without validating them against the destination buffer size. See the GitHub Security Advisory A-00000589 for additional technical context.
Attack Vector
Exploitation requires two preconditions. First, the attacker must operate a device that has successfully joined the target Zigbee network, meaning the attacker holds valid network credentials. Second, the attacker must wait for a victim device to issue a Simple_Desc_req query before responding with the malformed payload. Once both conditions are met, the attacker transmits the crafted ZDO response over the air. The receiving stack parses the response and performs the out-of-bounds write. No user interaction is required on the victim device.
No verified proof-of-concept code is publicly available. Refer to the vendor advisory for implementation specifics.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2026-85079
Indicators of Compromise
- Unexpected Simple_Desc_req responses originating from joined devices that do not match the queried endpoint descriptor format.
- Zigbee coordinator or router crashes, reboots, or stack faults correlated with ZDO traffic from a specific network address.
- Devices rejoining the network repeatedly after processing malformed descriptor responses.
Detection Strategies
- Deploy Zigbee sniffers to capture and inspect ZDO traffic for descriptor responses with inconsistent length fields.
- Correlate device firmware fault logs with timestamps of received Simple_Desc_req responses from untrusted endpoints.
- Monitor for anomalous join events followed by unsolicited ZDO responses to adjacent devices.
Monitoring Recommendations
- Enable verbose logging on Zigbee coordinators to capture ZDO transaction identifiers and response sources.
- Alert on repeated malformed ZDO frames flagged by stack parsers.
- Track firmware versions of all joined endpoints to confirm patch coverage.
How to Mitigate CVE-2026-85079
Immediate Actions Required
- Inventory all deployed devices running EmberZNet 9.1.1 or earlier and prioritize firmware updates.
- Review the Zigbee network device list and remove any untrusted or unknown devices that have joined.
- Rotate Zigbee network keys to invalidate credentials held by previously joined devices.
Patch Information
Silicon Labs has documented the fix in GitHub Security Advisory A-00000589. Operators should upgrade EmberZNet to a version later than 9.1.1 and reflash all affected endpoints. Confirm patch deployment by verifying the stack version reported by each device.
Workarounds
- Restrict network joins by disabling permit-join except during controlled commissioning windows.
- Enforce install-code based joining to prevent unauthorized devices from obtaining network credentials.
- Segment Zigbee networks so that compromise of one network cannot cascade to adjacent deployments.
# Configuration example
# Refer to the Silicon Labs advisory for vendor-specific firmware upgrade commands.
# No verified configuration snippet is published for this CVE.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

