dbcve.org
EmberznetApplication · Silabs

CVE-2026-47151

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 ClearWeekdaySchedule messages can trigger out-of-bounds writes into Door Lock schedule state. The size and location of this data is limited. These messages must come from a device that has already joined the network. Only devices supporting the Door Lock 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

Out-of-bounds write vulnerability in EmberZNet's Door Lock cluster. Malformed ClearWeekdaySchedule messages from authenticated network devices can write beyond buffer boundaries into door lock schedule state memory.

MitigationUpdate EmberZNet beyond v9.0.2 to patch the boundary check in ClearWeekdaySchedule handling; otherwise restrict network join permissions and monitor for anomalous door lock cluster traffic.

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
    Retrieve the EmberZNet stack version from your device firmware or SDK documentation. Common methods include checking the firmware build information, SDK release notes, or querying the device's Zigbee stack version property.
    Affected if The installed EmberZNet version is 9.0.2 or lower.
  2. Confirm Door Lock cluster implementation
    Inspect your device or application code to determine if the Zigbee Door Lock cluster (Cluster ID 0x0101) is implemented and enabled on your devices.
    Affected if The Door Lock cluster is active in your deployment.
  3. Verify ClearWeekdaySchedule functionality
    Examine whether the ClearWeekdaySchedule command handling is enabled within the Door Lock cluster implementation. This command is part of the door lock schedule management.
    Affected if ClearWeekdaySchedule command processing is supported in your door lock cluster code.
  4. Assess network authentication posture
    Review your Zigbee network access control settings to identify what devices are permitted to join as authenticated network nodes capable of sending door lock cluster commands.
    Affected if Untrusted or insufficiently vetted devices can join your Zigbee network as authenticated nodes.

You are affected if your EmberZNet version is 9.0.2 or lower, you have the Door Lock cluster with ClearWeekdaySchedule enabled, and untrusted devices can join your network as authenticated nodes.

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 beyond v9.0.2 to patch the boundary check in ClearWeekdaySchedule handling; otherwise restrict network join permissions and monitor for anomalous door lock cluster traffic.

Recommended fix Moderate confidence

EmberZNet 9.0.3 or later (consult Silicon Labs for the exact fixed release)

  1. 1. Identify all EmberZNet devices running version 9.0.2 or earlier in your network.
  2. 2. Consult the Silicon Labs release notes for EmberZNet versions newer than 9.0.2 to confirm the fix for CVE-2026-47151.
  3. 3. Download the latest stable EmberZNet stack from Silicon Labs (typically available via Simplicity Studio or the Silicon Labs website).
  4. 4. Update the firmware on affected devices, ensuring proper Zigbee network key handling during the upgrade process.
  5. 5. After updating, verify that the Door Lock cluster functionality operates correctly and no schedule data corruption occurs.
  6. 6. Monitor device behavior and network traffic to confirm the vulnerability has been mitigated.
Caveat firmware updates to embedded devices may require network rejoin and could affect existing device configurations; test in a staging environment first

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

Fix this in Emberznet Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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