Skip to main content
CVE-2025-10933VulnerabilityPublished

CVE-2025-10933: silabs.com Z-Wave Protocol Controller · Out-of-bounds Read

Affects silabs.com Z-Wave Protocol ControllerSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.7.1 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.7.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jan 2026

  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 2026-10-25.

What to do

Upgrade silabs.com Z-Wave Protocol Controller to 1.7.1.

Affected software

ProductAffectedFixed in
silabs.comZ-Wave Protocol ControllerAffected
  • <1.7.1
Fixed in
  • 1.7.1
GitHubZ-Wave Protocol Controllerpkg:github/Z-Wave Protocol ControllerOther threatsAffected
  • <1.7.1
Fixed in
  • 1.7.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor Silicon Labs and vendor advisories closely for official patches or firmware updates addressing CVE-2025-10933 and apply them promptly once available. 2. Implement network segmentation to isolate Z-Wave controllers from critical enterprise networks, limiting exposure to potential attackers. 3. Restrict network access to Z-Wave devices by enforcing strict firewall rules and access control lists, allowing only trusted management systems to communicate with them. 4. Employ intrusion detection and anomaly monitoring solutions tailored to IoT protocols to detect unusual traffic patterns or attempts to exploit memory vulnerabilities. 5. Conduct regular security assessments and penetration testing focused on IoT infrastructure to identify and remediate weaknesses. 6. Where possible, disable unused Z-Wave functionalities or services to reduce the attack surface. 7. Educate operational technology and IoT device administrators about the risks and signs of exploitation related to memory corruption vulnerabilities. 8. Consider deploying network-level encryption and authentication mechanisms for Z-Wave communications if supported by the device ecosystem to reduce interception risks. 9. Maintain an inventory of all Z-Wave devices and their firmware versions to prioritize remediation efforts effectively. 10. Collaborate with IoT device vendors and integrators to ensure secure configuration and timely updates.

Description

An integer underflow vulnerability in the Silicon Labs Z-Wave Protocol Controller can lead to out of bounds memory reads.

References

Community reviews

Loading reviews…