Skip to main content

Z-Wave SDK EUVDEUVD-2026-108187

| CVE-2026-89410 MEDIUM
Improper Validation of Specified Index, Position, or Offset in Input (CWE-1285)
2026-10-22 Silabs GHSA-39xw-g2p8-jwq5
5.1
CVSS 4.0 · Vendor: Silabs
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain physical access to device SPI bus
  2. Exploit
    Send malformed NCP SPI command
  3. Execution
    Trigger out-of-bounds read in SDK
  4. Impact
    Leak adjacent sensitive memory

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Hardware permission validation
Exploitation Conditions

Exploitation requires physical, board-level access to the device's NCP (Network Co-Processor) SPI bus - the serial interface between the host MCU and the Z-Wave radio - over which the attacker sends a malformed SPI command (AV:P). No software authentication is needed (PR:N) and no user interaction is required (UI:N), but the physical-access requirement is the dominant limiting factor: the flaw is not reachable over the Z-Wave RF network or any IP network from the provided vector. Affected scope is Z-Wave SDK version 8.1.1 and earlier. The precise malformed-command structure that triggers the out-of-bounds read is not described in the available sources.

Impact

This is a moderate, access-gated information-disclosure flaw rather than a top-tier emergency. The provided CVSS 4.0 vector (AV:P/AC:L/AT:N/PR:N/UI:N/VC:H) scores 5.1 and is driven almost entirely by the high confidentiality impact (VC:H); the Physical attack vector (AV:P) is what keeps the score moderate. Critically, the vector attacks the NCP (Network Co-Processor) SPI bus - an inter-chip serial interface on the device board - so a real attacker needs physical/hardware-level access to the host-to-radio SPI link, not network reachability. PR:N means no software credentials are required, but that is subordinate to the physical-access requirement. Signal alignment: the vendor-derived priority is 'this_month' (not act_now/emergency), there is no CISA KEV listing, and no EPSS probability was supplied in the input. No public exploit was identified in the provided data. The absence of EPSS leaves one standard exploitation-likelihood signal missing - this should be noted, not assumed low. Overall the signals are consistent: a genuine confidentiality bug that matters for threat models including local hardware tampering, supply-chain, or lab-access adversaries, but low urgency for remote mass-exploitation because of the physical vector.

Exploit ScenarioDerived

An attacker with physical access to a Z-Wave device's circuit board connects to the NCP SPI bus linking the host controller and the Z-Wave radio, then issues a malformed SPI command that triggers out-of-bounds reads, causing the SDK to return adjacent memory contents and leak sensitive information such as keys or network state. No public exploit code was identified in the provided data, and the specific trigger mechanics beyond 'malformed NCP SPI command' are not detailed in the available sources.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 22, 2026

Out-of-bounds reads in Silicon Labs Z-Wave SDK 8.1.1 and earlier allow an attacker with board-level access to the NCP SPI bus to leak sensitive memory contents from the device, rated CVSS 4.0 5.1. The flaw is not reachable over the Z-Wave RF mesh or any IP network: the assessed vector (AV:P/AC:L/PR:N/UI:N, C:H/I:N/A:N) requires physically attaching to the serial SPI interface between the host MCU and the Z-Wave radio and issuing a malformed command, which makes it a moderate, access-gated disclosure risk rather than a remotely exploitable emergency. No public exploit code has been identified at time of analysis, and no CISA KEV entry is associated with this issue; priority is tracked as remediation within the current month.

RemediationAI

The supplied intelligence does not list a specific fixed SDK version, so obtain the current patched Z-Wave SDK release and the corresponding NCP firmware from Silicon Labs and confirm the fixed build identifiers against advisory A-00000592 (https://github.com/SiliconLabsSoftware/docs-security-advisories/blob/main/Advisories/500-599/A-00000592.md) before deploying - vendor-released patch availability beyond that advisory is not independently confirmed in the provided data. Because exploitation requires physical access to the NCP SPI bus, the effective compensating controls are physical and board-level: restrict physical access to devices and their programming/debug headers to trusted personnel, and use tamper-evident enclosures or potting on exposed boards; the trade-off is increased manufacturing and servicing cost and reduced field-serviceability. Where the host-to-NCP SPI link can be disabled or moved behind an internal-only connector after provisioning, doing so removes the attack path, at the cost of losing local diagnostics; neither control substitutes for an SDK/firmware update, which remains the only complete fix.

Affected VersionsENISA

Z-Wave SDK 0 ≤8.1.1

Affected Packages

euvd z_wave_sdk no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The Z-Wave SDK implements the firmware and host-side interface for Silicon Labs Z-Wave devices, where the Network Co-Processor (NCP) is driven by a host MCU across an SPI bus using a proprietary command protocol. The weakness is classified as CWE-1285 (Improper Validation of Specified Index, Position, or Offset in Input), meaning the command handler accepts an attacker-supplied offset or length without bounds-checking it against the actual buffer, so a crafted NCP SPI command causes reads past the end of valid memory and returns adjacent contents to the caller. Because the SPI link is a local board-level interface, the attack surface is confined to the physical bus between host and radio rather than the RF protocol layer. The CPE cpe:2.3:a:silicon_labs:z-wave_sdk:*:*:*:*:*:*:*:* with the advisory's stated range covers SDK 8.1.1 and earlier; the precise malformed-command structure that triggers the out-of-bounds read is not described in the available sources, and the supplied evidence does not state whether the affected command set is enabled by default in all deployments.

Know when Z Wave Sdk gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Silabs) PRIMARY 5.1 MEDIUM
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 4.6 MEDIUM

Physical SPI-bus access gives AV:P; no credentials so PR:N; only an information leak, so C:H with I:N and A:N.

3.1 AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Silabs).

CVSS VectorVendor: Silabs

Attack Vector
Physical
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

In Z-Wave SDK 8.1.1 and earlier, a malformed NCP SPI command can trigger out-of-bounds reads that leak sensitive information.

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Medium
Silicon Labs Z-Wave SDK underpins most Z-Wave smart-home devices, a common but niche ecosystem
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy