dbcve.org
EmberznetApplication · Silabs

CVE-2026-47150

HIGH · 7.1 CVSS v3.1 Published 2026-06-25
Fix available
A fix is available. Upgrade to after 9.0.2 or later.
See remediation →
77/100
Remediation priority · High
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 IAS Zone enrollment messages can trigger an out-of-bounds state-table write and terminate the process. The size and location of this write is limited. These messages must come from a device that has already joined the network. Only devices supporting the IAS Zone 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, malformed IAS Zone enrollment messages trigger an out-of-bounds write to a state table, causing process termination. The attack requires a previously authenticated device on the network that supports the IAS Zone cluster, limiting the attack surface to authenticated Zigbee devices.

MitigationUpgrade EmberZNet beyond v9.0.2 when a patch is available. Until then, limit network join permissions and monitor for unexpected process terminations on devices running IAS Zone cluster implementations.

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
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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 the EmberZNet version
    Query the device or firmware for its EmberZNet software version using the product's CLI, API, or firmware metadata. Common commands include 'version', 'plugin stack-version', or inspecting firmware build information.
    Affected if The installed version is EmberZNet version 9.0.2 or any earlier version (versions <= 9.0.2).
  2. Confirm IAS Zone cluster implementation
    Inspect the device configuration, cluster list, or Zigbee endpoint settings to determine if the IAS Zone cluster (Cluster ID 0x0500) is included in the device's supported clusters or actively running.
    Affected if The device implements or exposes the IAS Zone cluster (Cluster ID 0x0500). The vulnerability only affects devices with this cluster enabled.
  3. Check network authentication exposure
    Review the Zigbee network configuration to identify whether unauthenticated devices can join the network, or whether only previously authenticated devices are permitted. Use the network controller or trust center logs to enumerate currently authenticated devices.
    Affected if The network permits authenticated devices that support IAS Zone to join, or already contains such devices. The attacker requires a previously authenticated device on the network.
  4. Monitor for IAS Zone related process terminations
    Review system logs, debug logs, or crash reports on the EmberZNet device for unexpected process terminations or crashes that occur when processing IAS Zone enrollment messages.
    Affected if Unexpected process terminations are observed on devices running IAS Zone cluster implementations.

A device is affected if it runs EmberZNet version 9.0.2 or earlier AND implements the IAS Zone cluster, with an authenticated IAS Zone-capable device present on the same network.

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

Upgrade EmberZNet beyond v9.0.2 when a patch is available. Until then, limit network join permissions and monitor for unexpected process terminations on devices running IAS Zone cluster implementations.

Recommended fix Moderate confidence

EmberZNet version newer than 9.0.2 (consult Silicon Labs for exact fixed release)

  1. 1. Identify all EmberZNet devices in your deployment running version 9.0.2 or earlier.
  2. 2. Consult the Silicon Labs official release notes and security advisories for EmberZNet to determine the specific version that addresses CVE-2026-47150.
  3. 3. Upgrade all affected EmberZNet devices to the fixed release version (typically a point release after 9.0.2).
  4. 4. After upgrading, verify that the IAS Zone cluster functionality operates correctly with the new version.
  5. 5. Ensure that only authenticated devices that have completed the join process can communicate on the network, as the attack requires a device that has already joined.
Caveat Review Silicon Labs release notes for the fixed version for any API changes or deprecations that may affect your application

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

Fix this in Emberznet Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing10.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,300
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47150 — 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-47150 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