CVE-2026-47148: EmberZNet Groups Cluster Denial of Service Vulnerability
EmberZNet versions 9.0.2 and earlier contain a denial-of-service vulnerability triggered by malformed GetGroupMembership commands. An attacker with network access and prior device enrollment can send a specially crafted message that causes the receiving device to read past the end of its message buffer, crashing the process. The vulnerability does not leak data and only affects devices that support the Groups cluster—a subset of EmberZNet deployments.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 6.5 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weaknesses (CWE)
- CWE-125
- Affected products
- 1 configuration(s)
- Published / Modified
- 2026-06-25 / 2026-06-25
NVD description (verbatim)
In EmberZNet v9.0.2 and earlier, malformed GetGroupMembership commands can trigger repeated reads past the end of the message payload and terminate the process. These messages must come from a device that has already joined the network, and no information leakage back to the sender was observed. Only devices supporting the Groups cluster may be impacted.
2 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-47148 is a buffer over-read flaw (CWE-125) in EmberZNet's Groups cluster command handling. When a device receives a GetGroupMembership command with a malformed payload, the parser reads beyond the actual message boundary, leading to uncontrolled memory access and process termination. The vulnerability requires the attacker's device to have already completed the network join process, limiting the attack surface to authenticated participants. No information disclosure was observed during analysis, making this primarily an availability issue.
Business impact
Organizations deploying EmberZNet-based mesh networks—commonly found in smart home, industrial IoT, and building automation systems—face potential service disruptions. An attacker already present on the network can selectively disable devices supporting the Groups cluster, fragmenting network topology and interrupting automation workflows. Recovery requires manual device restart or network remediation, introducing operational downtime and administrative overhead.
Affected systems
Silicon Labs EmberZNet version 9.0.2 and all earlier versions are vulnerable. The impact is limited to devices that have the Groups cluster enabled; devices without this cluster are unaffected. EmberZNet is widely used in Zigbee-based solutions for home and industrial automation.
Exploitability
Exploitation requires network-level access and prior successful device enrollment on the target network. An attacker cannot remotely join a closed network to launch this attack; they must either be a legitimate member already or gain access through network compromise elsewhere. Once positioned, crafting the malformed command is straightforward. The CVSS score of 6.5 (Medium) reflects the moderate attack complexity combined with high availability impact and the prerequisite of network membership.
Remediation
Silicon Labs has addressed this issue in EmberZNet versions after 9.0.2; verify the specific patched version in the official Silicon Labs security advisory. Organizations should upgrade to the latest stable release that includes this fix. For devices that cannot be immediately patched, network segmentation and access controls can reduce exposure by limiting which devices can join the mesh.
Patch guidance
Review Silicon Labs' official product security page and EmberZNet release notes to identify the minimum patched version for your deployment. Upgrade affected devices in a staged rollout to prevent network-wide disruption. Firmware updates for EmberZNet devices may require physical access or specific bootloader sequences; consult your device manufacturer's update procedure. After patching, verify that Groups cluster functionality is still operational in your automation workflows.
Detection guidance
Monitor for unexpected device disconnections or repeated restart cycles among EmberZNet devices, particularly those with Groups cluster enabled. Network-level detection is challenging because the malformed GetGroupMembership command appears as standard Zigbee traffic; focus on behavioral anomalies such as sudden loss of devices and rapid reconnection attempts. Capture Zigbee frames in suspicious windows and correlate with device log entries showing buffer-related faults or stack traces.
Why prioritize this
This vulnerability merits prompt attention for organizations running critical EmberZNet infrastructure, but it is not an emergency requiring emergency patching across the estate. The requirement for prior network enrollment significantly limits blast radius compared to unauthenticated remote exploits. Prioritize patching devices in high-availability environments (lighting systems, HVAC controls) and those exposed to untrusted network participants. Less critical systems can be updated within the next regular maintenance window.
Risk score, explained
The CVSS 3.1 score of 6.5 (Medium) reflects a straightforward network-based attack (AV:N) with low attack complexity (AC:L), requiring authenticated network participation (PR:L), no user interaction (UI:N), single scope (S:U), and no confidentiality or integrity impact (C:N/I:N) but high availability impact (A:H). The score appropriately balances the ease of exploitation once an attacker is on the network against the prerequisite of prior enrollment and the absence of data exposure.
Frequently asked questions
Can this vulnerability be exploited from outside the EmberZNet network?
No. The attacker must be a device that has already joined the target network and completed the enrollment process. External attackers cannot launch this attack without first compromising network access or credentials.
Does this vulnerability result in data theft or information disclosure?
No. The vulnerability causes a denial-of-service by triggering a buffer over-read that crashes the process. No information leakage back to the attacker was observed during analysis. The risk is availability, not confidentiality or integrity.
Are all EmberZNet devices affected?
No. Only devices with the Groups cluster enabled are vulnerable. Many EmberZNet deployments do not use group messaging; review your device configuration and cluster assignments to determine if you are affected.
What is the practical impact if a device is compromised by this vulnerability?
The affected device will crash and disconnect from the network. It will require manual restart or power-cycle to recover. In large deployments, this could fragment the mesh and disrupt automation until the device rejoins and routing is re-established.
This analysis is based on information current as of the published CVE date. Verify all patch version numbers and remediation steps against the official Silicon Labs security advisory before deployment. Organizations should conduct internal testing in non-production environments prior to production rollout. SEC.co does not guarantee the completeness or accuracy of third-party vendor patch information; consult official vendor guidance for definitive remediation steps. Source: NVD (public-domain), retrieved 2026-08-03. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-4526MEDIUMEmberZNet ZCL Out-of-Bounds Read DoS Vulnerability (v9.0.2 and Earlier)
- CVE-2026-47149MEDIUMEmberZNet Door Lock Denial of Service Vulnerability
- CVE-2026-47154MEDIUMEmberZNet Simple Metering Out-of-Bounds Read DoS Vulnerability
- CVE-2020-9711MEDIUMAdobe Acrobat Reader Out-of-Bounds Read Memory Disclosure
- CVE-2020-9713MEDIUMAdobe Acrobat Reader Memory Disclosure Vulnerability
- CVE-2025-15661MEDIUMlibssh2 Out-of-Bounds Heap Read in SFTP Symlink Handling
- CVE-2025-70101MEDIUMlwext4 1.0.0 Out-of-Bounds Read Denial of Service
- CVE-2026-0127MEDIUMAndroid Out-of-Bounds Read in Communication Processor – Impact & Patch Guidance