CVE-2026-89409 Silicon Labs CVE debrief

Who should care

Defenders responsible for Z-Wave devices and networks should assess exposure and prioritize verification of Z-Wave SDK versions in use, especially for devices that have already joined the network. This includes operators, platform administrators, vulnerability management teams, and security teams who need to review the affected scope, severity, and vendor guidance.

Why it matters

This vulnerability allows for the removal of nodes from the network due to missing checks in the ZWAVE_CMD_NODES_EXIST handler. Defenders should prioritize verifying Z-Wave SDK versions and assessing exposure to devices that have already joined the network.

• Verification of Z-Wave SDK versions in use is required to determine exposure.
• Node removal can occur if the ZWAVE_CMD_NODES_EXIST handler is exploited.
• Defenders should monitor network activity for suspicious Z-Wave device interactions.

Technical summary

The Z-Wave SDK versions 8.1.1 and earlier (for 700/800 series devices) and 6.85.02 and earlier (for 500 series devices) are affected by a vulnerability in the ZWAVE_CMD_NODES_EXIST handler. This handler requires messages to come from a device that has already joined the network. The vulnerability allows for the removal of nodes from the network due to missing checks. Defenders should prioritize verifying the versions of Z-Wave SDK in use and assessing exposure to devices that have already joined the network, especially for 700/800 and 500 series devices.

Defensive priority

Defenders should prioritize verifying the versions of Z-Wave SDK in use and assessing exposure to devices that have already joined the network.

Recommended defensive actions

• Verify Z-Wave SDK versions in use and assess exposure to devices that have already joined the network.
• Implement checks for ZWAVE_CMD_NODES_EXIST handler to prevent node removal.
• Monitor network for suspicious activity related to Z-Wave devices.
• 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 source item provide details on the vulnerability, affected versions, and a reference to a vendor advisory. The source item provides additional information on the vulnerability. The CVE Program record was published on 2026-10-22T13:50:04.309Z and has not been modified since then. However, defenders should verify the affected scope, severity, and vendor guidance through official channels.

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.