dbcve.org
EmberznetApplication · Silabs

CVE-2026-47146

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 Color Control messages can lead to asserts that terminate the process. These messages must come from a device that has already joined the network. Only devices supporting the Color Control 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 · high confidence

In EmberZNet Zigbee stack versions 9.0.2 and earlier, specially crafted malformed Color Control cluster messages trigger assertion failures that crash the process. An attacker must have a previously authenticated device on the network to send these malicious packets, making this a network-adjacent denial-of-service vulnerability affecting only devices implementing the Color Control cluster.

MitigationApply the EmberZNet vendor patch for this vulnerability and update all affected devices to the patched firmware version. Network segmentation and monitoring for anomalous Color Control messages can provide interim detection capability.

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 firmware version
    Retrieve the firmware version from the device firmware image, boot logs, or management interface. This is typically displayed in startup diagnostics or available via debug commands such as 'version' or 'info' depending on the device implementation.
    Affected if The installed EmberZNet version is 9.0.2 or earlier.
  2. Confirm Color Control cluster implementation
    Examine the device's Zigbee cluster configuration or endpoint description to determine whether the Color Control cluster (cluster ID 0x0300) is included in any of the device's endpoints.
    Affected if The device implements the Color Control cluster (Zigbee cluster ID 0x0300).
  3. Verify network-adjacent attack surface
    Review network configuration logs or access control settings to confirm whether unauthenticated or previously authenticated devices can send Zigbee cluster messages to the affected device.
    Affected if The device accepts Color Control cluster messages from other network devices without additional validation beyond standard Zigbee authentication.

A device is affected if it runs EmberZNet version 9.0.2 or earlier AND implements the Color Control cluster (cluster ID 0x0300), making it vulnerable to denial-of-service from malformed packets sent by authenticated network devices.

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

Apply the EmberZNet vendor patch for this vulnerability and update all affected devices to the patched firmware version. Network segmentation and monitoring for anomalous Color Control messages can provide interim detection capability.

Recommended fix Moderate confidence

EmberZNet version newer than 9.0.2 (specific fixed release available from Silicon Labs)

  1. 1. Identify all EmberZNet devices running version 9.0.2 or earlier in your network
  2. 2. Check Silicon Labs documentation or release notes for the fixed version (version newer than 9.0.2)
  3. 3. Plan a maintenance window for the upgrade, ensuring network continuity
  4. 4. Upgrade EmberZNet to the fixed release version
  5. 5. After upgrade, verify that the Color Control cluster is functioning properly
  6. 6. Test with legitimate Color Control commands to confirm the assert no longer triggers on malformed messages
Caveat Check Silicon Labs release notes for any breaking changes between 9.0.2 and the fixed version, particularly around Zigbee cluster behavior

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

Fix this in Emberznet Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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