CVE-2026-47149
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 · uneditedIn EmberZNet v9.0.2 and earlier, malformed or out-of-range Door Lock user identifiers can trigger out-of-bounds table reads 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 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 confidenceIn EmberZNet Zigbee stack versions 9.0.2 and earlier, the Door Lock cluster implementation lacks proper bounds validation when processing user identifiers. Crafted messages with out-of-range user IDs cause the stack to read beyond allocated table boundaries, triggering a fatal exception that terminates the process. Exploitation requires an already-authenticated device on the network to send malformed Door Lock commands, resulting in denial of service for the affected lock device.
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<= 9.0.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the EmberZNet version in useConsult the device firmware documentation, release notes, or query the network coordinator for the EmberZNet stack version. The version is typically displayed in the device information or firmware metadata.Affected if The installed EmberZNet version is 9.0.2 or earlier.
-
Confirm Door Lock cluster implementationReview the device or application configuration to verify whether the Door Lock cluster (Zigbee cluster ID 0x0101) is implemented and actively processing user identifiers.Affected if Door Lock cluster is implemented and configured to handle user credential operations.
-
Monitor for fatal exceptions during Door Lock operationsExamine device logs, network management logs, or debugging outputs for fatal exceptions or unexpected device resets that occur when Door Lock commands containing user identifiers are processed.Affected if Devices exhibit fatal exceptions or crashes specifically when processing Door Lock commands with user IDs.
-
Check network segmentation and device authenticationReview network access controls to determine if unauthenticated or unauthorized devices can send commands to Door Lock devices on the network.Affected if Authenticated devices on the network can send malformed Door Lock commands to the affected lock device.
A user is affected if their EmberZNet version is 9.0.2 or earlier, they have Door Lock cluster implementation in use, and an authenticated network device can send crafted Door Lock commands with out-of-range user IDs to trigger the bounds checking flaw.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataDeploy the vendor-supplied EmberZNet firmware update addressing bounds checking in the Door Lock cluster. Until patched, isolate Door Lock devices on a dedicated network segment and monitor for anomalous device behavior to detect exploitation attempts.
- Consultation8.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,008.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47149 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-47149 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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