dbcve.org
EmberznetApplication · Silabs

CVE-2026-47145

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 versions 9.0.2 and earlier, the Zigbee ZCL Color Control cluster implementation lacks proper input validation for incoming messages. When a malformed Color Control message is received from an authenticated network device, it triggers an assertion failure that terminates the process, causing a denial of service.

MitigationImplement robust input validation and error handling in the Color Control cluster message parser to gracefully handle malformed messages instead of asserting. Additionally, enforce network access controls to prevent unauthorized devices from joining.

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
    Locate the EmberZNet version information in your device firmware, software manifest, or runtime library version (often found in about screens, firmware headers, or library metadata)
    Affected if version is 9.0.2 or earlier
  2. Confirm version range is within affected scope
    Compare your installed version against the affected range: versions 9.0.2 and earlier
    Affected if installed version is 9.0.2 or lower
  3. Verify Zigbee ZCL Color Control cluster is implemented
    Inspect your EmberZNet configuration or application code to determine if the ZCL Color Control cluster (cluster ID 0x0300) is included in the Zigbee endpoint configuration
    Affected if Color Control cluster is present in your Zigbee device configuration
  4. Confirm device accepts Zigbee network messages
    Check your EmberZNet network configuration to verify the device is configured to accept incoming Zigbee messages from other devices on the network
    Affected if device accepts incoming Zigbee messages from other network devices

You are affected if your device runs EmberZNet version 9.0.2 or earlier, has the ZCL Color Control cluster enabled, and accepts incoming Zigbee network messages that could contain malformed Color Control 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

Implement robust input validation and error handling in the Color Control cluster message parser to gracefully handle malformed messages instead of asserting. Additionally, enforce network access controls to prevent unauthorized devices from joining.

Recommended fix Moderate confidence

EmberZNet 9.0.3 or later

  1. 1. Identify the current EmberZNet version in use by checking the firmware or software build
  2. 2. Obtain the latest EmberZNet release from Silicon Labs (typically available through their GitHub repository or support portal)
  3. 3. Verify the release notes for the fixed version to confirm the Color Control assert vulnerability is addressed
  4. 4. Update the EmberZNet firmware/software to version 9.0.3 or later
  5. 5. After upgrade, test Color Control cluster functionality to ensure proper operation
  6. 6. Re-validate network join and communication for devices using the Color Control cluster
Caveat Review Silicon Labs release notes for any API changes or migration requirements between 9.0.2 and the target version

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

Fix this in Emberznet Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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