Is CVE-2026-85079 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-85079 being exploited in the wild.

How severe is CVE-2026-85079?

Informational severity, published 22 October 2026.

Which products and versions are affected?

Silicon Labs EmberZNet 9.1.1 and earlier; Silicon Labs GSDK all released versions (unfixed); Silicon Labs SiSDK 2026.6.1 and earlier.

How is CVE-2026-85079 attacked?

It is attacked from the adjacent network or with local access, in a software library.

Am I affected by CVE-2026-85079?

Check whether you run Silicon Labs EmberZNet, Silicon Labs GSDK or Silicon Labs SiSDK at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-85079: Silicon Labs EmberZNet out-of-bounds write in Simple_Desc_req

CVE-2026-85079 · Severity: info · Published 2026-10-22

EmberZNet is a Zigbee networking SDK used in IoT and embedded devices. A malformed response to a network descriptor request can trigger an out-of-bounds memory write, potentially allowing remote code execution if the device has not disabled code execution from RAM. The attacker must already be on the Zigbee network and wait for the target device to initiate a descriptor query.

Technologies: Silicon Labs EmberZNet, Silicon Labs SiSDK. Vendors: Silicon Labs.

Quick answers

Is CVE-2026-85079 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-85079 being exploited in the wild.
How severe is CVE-2026-85079?: Informational severity, published 22 October 2026.
Which products and versions are affected?: Silicon Labs EmberZNet 9.1.1 and earlier; Silicon Labs GSDK all released versions (unfixed); Silicon Labs SiSDK 2026.6.1 and earlier.
Is there a fix for CVE-2026-85079?: Yes: fixed in SiSDK 2026.6.2 or later; GSDK fix not available at time of publication. Until then: Enable the Memory Protection Unit (MPU) by including the "Platform > Security > Memory Protection Unit > Simple MPU" component in Simplicity Studio to make RAM non-executable and prevent code injection attacks. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-85079 attacked?: It is attacked from the adjacent network or with local access, in a software library.
Am I affected by CVE-2026-85079?: Check whether you run Silicon Labs EmberZNet, Silicon Labs GSDK or Silicon Labs SiSDK at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: SiSDK 2026.6.2 or later; GSDK fix not available at time of publication

Enable the Memory Protection Unit (MPU) by including the "Platform > Security > Memory Protection Unit > Simple MPU" component in Simplicity Studio to make RAM non-executable and prevent code injection attacks.

Technical details

An out-of-bounds write vulnerability exists in the Simple_Desc_req response handler in EmberZNet 9.1.1 and earlier. The vulnerability requires network adjacency and a pre-joined network position (authenticated attacker), plus a race condition waiting for the target to send a Simple_Desc_req. Exploitation leads to code execution in RAM if memory protection is not enabled; the attack has no cluster dependency.

Affected products

Silicon Labs EmberZNet 9.1.1 and earlier
Silicon Labs SiSDK 2026.6.1 and earlier
Silicon Labs GSDK all released versions (unfixed)

Timeline

2026-10-22: disclosed

References

https://github.com/SiliconLabsSoftware/docs-security-advisories/blob/main/Advisories/500-599/A-00000589.md

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.