CVE-2026-47151 Silicon Labs CVE debrief

Who should care

Defenders responsible for Door Lock devices using EmberZNet v9.0.2 and earlier should assess exposure and verify the network for potential malicious activity. They should also review compensating controls for exposed systems while remediation is scheduled and verified, and check relevant monitoring, detection, and logs for exposed assets that need extra review.

Why it matters

Defenders should prioritize verifying exposure of Door Lock devices using EmberZNet v9.0.2 and earlier, and assess the network for potential malicious activity. The vulnerability allows for out-of-bounds writes into Door Lock schedule state, but the size and location of the data is limited.

• Verify exposure of Door Lock devices using EmberZNet v9.0.2 and earlier
• Assess the network for potential malicious activity from devices that have joined the network
• Monitor for unusual activity from devices that have joined the network

Technical summary

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. The vulnerability allows for out-of-bounds writes into Door Lock schedule state, but the size and location of the data is limited. Defenders should prioritize verifying exposure of Door Lock devices using EmberZNet v9.0.2 and earlier, and assess the network for potential malicious activity.

Defensive priority

Defenders should prioritize verifying exposure of Door Lock devices using EmberZNet v9.0.2 and earlier, and assess the network for potential malicious activity.

Recommended defensive actions

• Verify exposure of Door Lock devices using EmberZNet v9.0.2 and earlier
• Assess the network for potential malicious activity
• Monitor for unusual activity from devices that have joined the network
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD detail page provide limited information about the vulnerability. The size and location of the data that can be written out-of-bounds is limited, and these messages must come from a device that has already joined the network.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.