Is CVE-2026-17610 exploited in the wild?

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

How severe is CVE-2026-17610?

Informational severity, published 28 August 2026.

Which products and versions are affected?

Silicon Labs EFR32MG24 running concurrent multiprotocol Zigbee and Thread; Silicon Labs EFR32MG26 running concurrent multiprotocol Zigbee and Thread; Silicon Labs SiSDK 2026.6.0 and earlier.

Is there a fix for CVE-2026-17610?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-17610 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-17610?

Check whether you run Silicon Labs EFR32MG24, Silicon Labs EFR32MG26 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-17610: Silicon Labs SiSDK denial of service in multiprotocol mode

CVE-2026-17610 · Severity: info · Published 2026-08-28

SiSDK is a software development kit used to develop applications for Silicon Labs wireless microcontroller devices. Under high network traffic loads, a dropped ACK (acknowledgment packet) can cause a denial of service condition in devices running concurrent Zigbee and Thread protocols, potentially disrupting IoT and smart home deployments that rely on these wireless protocols.

Technologies: Silicon Labs SiSDK. Vendors: Silicon Labs.

Quick answers

Is CVE-2026-17610 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-17610 being exploited in the wild.
How severe is CVE-2026-17610?: Informational severity, published 28 August 2026.
Which products and versions are affected?: Silicon Labs EFR32MG24 running concurrent multiprotocol Zigbee and Thread; Silicon Labs EFR32MG26 running concurrent multiprotocol Zigbee and Thread; Silicon Labs SiSDK 2026.6.0 and earlier.
Is there a fix for CVE-2026-17610?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-17610 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-17610?: Check whether you run Silicon Labs EFR32MG24, Silicon Labs EFR32MG26 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.

Technical details

This is a denial of service vulnerability affecting SiSDK v2026.6.0 and earlier that manifests when EFR32MG24 and EFR32MG26 devices operate in multiprotocol mode with concurrent Zigbee and Thread enabled. The root cause is improper handling of network ACKs under high traffic loads, leading to dropped acknowledgments. The vulnerability is triggered by network conditions (high traffic) and is reachable to any entity that can generate sustained network traffic toward the affected device. Attackers can cause service interruptions on vulnerable wireless networks. Patches are expected in later versions of SiSDK.

Affected products

Silicon Labs SiSDK 2026.6.0 and earlier
Silicon Labs EFR32MG24 running concurrent multiprotocol Zigbee and Thread
Silicon Labs EFR32MG26 running concurrent multiprotocol Zigbee and Thread

Timeline

2026-08-28: disclosed: CVE-2026-17610 published

References

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