# CVE-2025-10693: Silicon Labs Z-Wave PIR Sensor Joins Network as Non-Secure

> Attackers can force Z-Wave PIR sensors to join networks insecurely if SmartStart inclusion fails, bypassing expected security protocols.

- **Severity:** High 7.6 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Oct 2025
- **Updated:** 31 Oct 2025
- **Also known as:** GHSA-v97f-7x7p-g6cq

## What is CVE-2025-10693?

CVE-2025-10693 is a high-severity vulnerability in silabs.com Silicon Labs Z-Wave SDK, published on 31 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-757 (Selection of Less-Secure Algorithm During Negotiation)

## Which versions are affected by CVE-2025-10693?


## How do I fix CVE-2025-10693?

No fix has been published for CVE-2025-10693 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-10693 being exploited?

There is no known exploitation of CVE-2025-10693 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10693 and fix it if it is affected.

What it is: CVE-2025-10693 is a high-severity vulnerability in silabs.com Silicon Labs Z-Wave SDK, published on 31 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-10693 in the wild and no public exploit code.

Affected product: silabs.com Silicon Labs Z-Wave SDK. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-10693/ (Markdown: https://insights.sbomify.com/CVE-2025-10693/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-10693
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-10693
- OSV: https://osv.dev/vulnerability/CVE-2025-10693

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-10693/
Summaries are generated and may contain mistakes; the official description above is the record.