{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-10693 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-10693 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-10693 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2025-10693 in the wild and no public exploit code.\n\nAffected 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.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-10693/ (Markdown: https://insights.sbomify.com/CVE-2025-10693/index.md)","id":"CVE-2025-10693","markdown":"https://insights.sbomify.com/CVE-2025-10693/index.md","name":"CVE-2025-10693","record":{"aliases":["GHSA-v97f-7x7p-g6cq"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Z-Wave PIR Sensor","requires_auth":"none","summary":"Attackers can force Z-Wave PIR sensors to join networks insecurely if SmartStart inclusion fails, bypassing expected security protocols.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Silabs","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-757","name":"Selection of Less-Secure Algorithm During Negotiation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Silicon Labs Z-Wave PIR Sensor Joins Network as Non-Secure","id":"CVE-2025-10693","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in UserFeedback – Create Interactive Feedback Form, User Surveys, and Polls in Seconds","id":"CVE-2025-10694"},"packages":[],"prev":{"headline":"OpenSupports 4.11.0 — SQL Injection","id":"CVE-2025-10692"},"products":["Silicon Labs Z-Wave SDK"],"published":"2025-10-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-31","vendors":["silabs.com"]},"summary":"Attackers can force Z-Wave PIR sensors to join networks insecurely if SmartStart inclusion fails, bypassing expected security protocols.","url":"https://insights.sbomify.com/CVE-2025-10693/"}