Skip to main content
VulnerabilityPublished

CVE-2025-10693: silabs.com Silicon Labs Z-Wave SDK · Algorithm Downgrade

Affects silabs.com Silicon Labs Z-Wave SDKSource CVE Database V5

0

Not known to be exploited · CVSS 7.6 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
silabs.com Silicon Labs Z-Wave SDKAffected
  • =2025.6.0
Fixed in–

AI-suggested

  1. Immediately audit all Z-Wave PIR sensors and related devices to identify those running the vulnerable SDK version 2025.6.0 or 2025.6.1.
  2. Engage with Silicon Labs or device vendors for patches or updated SDK versions that address the SmartStart Inclusion failure and enforce secure onboarding.
  3. Implement strict monitoring of device onboarding processes to detect and alert on any failures or non-secure device joins.
  4. Enforce network segmentation to isolate IoT devices from critical infrastructure and sensitive data networks.
  5. Disable or restrict SmartStart Inclusion where possible until patches are applied, or require manual secure inclusion procedures.
  6. Educate users and administrators on the risks of insecure device onboarding and the importance of verifying device security status post-inclusion.
  7. Employ network-level intrusion detection systems tuned to detect anomalous Z-Wave traffic patterns indicative of downgrade or unauthorized device behavior.
  8. Maintain an inventory of all Z-Wave devices and their firmware versions to facilitate timely updates and vulnerability management.
  9. Consider alternative secure IoT protocols or devices if patching is delayed or unsupported.
  10. Review and update incident response plans to include IoT-specific attack scenarios involving algorithm downgrade vulnerabilities.

Description

When SmartStart Inclusion fails during the onboarding of a Z-Wave PIR sensor, the sensor will join the network as a non-secure device. This vulnerability exists in Silicon Labs' Z-Wave PIR Sensor Reference design delivered as part of SiSDK v2025.6.0 and v2025.6.1.

References

Community reviews

Loading reviews…