dbcve.org
EmberznetApplication · Silabs

CVE-2026-47148

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-25
Fix available
A fix is available. Upgrade to after 9.0.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

In EmberZNet v9.0.2 and earlier, the Groups cluster implementation contains a buffer over-read vulnerability where malformed GetGroupMembership commands cause repeated reads past the end of the message payload, leading to process termination. The attacker requires a pre-authenticated device already joined to the Zigbee network to send these malicious commands.

MitigationUpdate EmberZNet to a patched version once available from Silicon Labs. Network segmentation and restricting joining of untrusted devices can reduce attack surface until the update is deployed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EmberznetApplication
Affected:<= 9.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify EmberZNet version
    Query the device or firmware for the installed EmberZNet version number
    Affected if The installed version is 9.0.2 or any earlier version (9.0.0 through 9.0.2)
  2. Confirm Groups cluster is active
    Check the Zigbee device configuration or cluster list to verify the Groups cluster (cluster ID 0x0004) is implemented and enabled
    Affected if The Groups cluster is present and actively processing GetGroupMembership commands
  3. Verify device accepts Zigbee network commands
    Confirm the device is joined to a Zigbee network and will accept commands from other network devices
    Affected if The device is operational on a Zigbee network and can receive GetGroupMembership commands from joined devices
  4. Check for pre-authenticated devices on network
    Review the network neighbor table or device association list to identify joined devices
    Affected if There are devices joined to the same Zigbee network that could send malicious GetGroupMembership commands

You are affected if your EmberZNet version is 9.0.2 or earlier AND your device has the Groups cluster enabled AND it is part of a Zigbee network where an authenticated device could send malformed GetGroupMembership commands.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 9.0.2
Interim mitigation

Update EmberZNet to a patched version once available from Silicon Labs. Network segmentation and restricting joining of untrusted devices can reduce attack surface until the update is deployed.

Recommended fix Moderate confidence

EmberZNet version newer than 9.0.2 (check Silicon Labs for the specific fixed release)

  1. 1. Identify all EmberZNet devices in the network running version 9.0.2 or earlier.
  2. 2. Consult the Silicon Labs release notes or software change notifications for EmberZNet versions after 9.0.2 to confirm the fixed release.
  3. 3. Obtain the updated EmberZNet stack image from Silicon Labs official distribution channels.
  4. 4. Upgrade each affected device to the fixed EmberZNet version following Silicon Labs standard firmware update procedures.
  5. 5. Verify the upgrade was successful and confirm the Groups cluster functionality operates normally.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Emberznet Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47148 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47148 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data