Skip to main content

WiseConnect (SiWx917/RS9116W) CVE-2026-65935

| EUVDEUVD-2026-58082 HIGH
Authentication Bypass by Primary Weakness (CWE-305)
2026-08-13 Silabs GHSA-gf4f-g545-p55p
7.6
CVSS 4.0 · Vendor: Silabs
View

Attack ChainAIDerived

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

  1. Access
    Position within Bluetooth radio range
  2. Delivery
    Initiate BLE legacy Passkey Entry pairing request
  3. Exploit
    Intercept pairing handshake and manipulate TK value
  4. Execution
    Forge valid Confirm values
  5. Persist
    Bypass authentication and complete pairing
  6. Impact
    Access protected BLE GATT services on target device

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Primary weakness mitigation
Exploitation Conditions

BLE legacy pairing (not BLE Secure Connections) must be enabled and active on the target RS9116W or SiWx917 device, and the Passkey Entry association model must be in use for the targeted pairing session. The attacker must be within Bluetooth radio range (adjacent network - CVSS AV:A). AT:P in the CVSS 4.0 vector confirms specific attack timing requirements: the TK manipulation must occur during the active pairing handshake window. Exploitation is not possible against devices using BLE Secure Connections, Just Works association, or OOB pairing. No authentication or user interaction is required once the attacker is in range and a pairing event is occurring.

Impact

The CVSS 4.0 score of 7.6 reflects meaningful but proximity-constrained risk: AV:A (Bluetooth adjacency, typically 10-100 m) limits mass internet-scale exploitation, while PR:N and UI:N mean no credentials or victim interaction are needed once within range. AT:P in the CVSS 4.0 vector confirms that specific attack timing or conditions are required (TK manipulation during the pairing handshake window), introducing some operational complexity. VC:H and VI:H indicate full compromise of data confidentiality and integrity on the affected device. No EPSS score is available in the provided data. The absence of a CISA KEV entry indicates no confirmed active exploitation at time of analysis; however, the academic paper (arxiv 2409.02905) publicly discloses the technique, lowering the bar for capable adversaries. Real-world risk is highest in industrial IoT, medical device, and consumer electronics deployments relying on BLE pairing security with legacy mode enabled.

Exploit ScenarioDerived

An attacker carrying a Bluetooth-capable device (laptop or embedded radio) positions themselves within Bluetooth range of a deployed RS9116W or SiWx917 device. The attacker initiates a BLE pairing request using Passkey Entry and, during the Confirm/Random exchange, manipulates the TK value to forge valid confirm values - bypassing the authentication check and completing pairing without knowing the actual passkey. The academic paper at arxiv.org/pdf/2409.02905 (vulnerability B-E3) documents the technical approach, providing sufficient detail for a capable attacker to replicate the technique.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.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 – Aug 13, 2026

Bluetooth LE legacy pairing authentication in Silicon Labs RS9116W and SiWx917 wireless modules (WiseConnect SDK) can be bypassed by manipulating the Temporary Key (TK) value during Passkey Entry association, allowing an adjacent unauthenticated attacker to pair with the target device without possessing the correct passkey. Successful exploitation yields high confidentiality and integrity impact on the vulnerable system. The vulnerability is academically documented as B-E3 in a published research paper (arxiv.org/pdf/2409.02905); no public exploit tool or CISA KEV entry has been identified at time of analysis.

RemediationAI

Consult the Silicon Labs security advisory at https://community.silabs.com/068Vm00000x0Yqy for patched WiseConnect SDK versions and apply the vendor-supplied update as the primary fix. A specific patched release version is not independently confirmed from available data - verify with the advisory before deployment. As an immediate compensating control, disable BLE legacy pairing and configure devices to require BLE Secure Connections only (which uses ECDH and is not susceptible to TK manipulation); note this may break compatibility with older BLE hosts. If legacy pairing must be retained, switch the association model from Passkey Entry to Out-of-Band (OOB) pairing, which does not rely on the TK-derived confirm exchange. Additionally, restrict physical Bluetooth radio exposure by deploying affected devices in access-controlled environments to limit attacker adjacency.

Affected VersionsENISA

WiseConnect 4.0.0 ≤4.*.*
WiseConnect 2.0.0 ≤2.*.*

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

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

Technical ContextAI · show details

Bluetooth LE legacy pairing (pre-Secure Connections) uses a Temporary Key (TK) derived from the passkey in the Confirm/Random value exchange (the LE Legacy Pairing model defined in Bluetooth Core Specification). In the Passkey Entry association model, the TK encodes the passkey and is used to generate confirm values that both sides verify. CWE-305 (Authentication Bypass by Primary Weakness) describes the root cause: the implementation in Silicon Labs WiseConnect software (CPE: cpe:2.3:a:silabs.com:wiseconnect) for RS9116W and SiWx917 SoCs does not properly validate or protect the TK value, permitting an attacker to inject or manipulate it to forge valid confirm values and complete pairing without the correct passkey. The vulnerability is specific to BLE legacy pairing and does not affect BLE Secure Connections, which use ECDH key exchange.

Know when Wiseconnect 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 7.6 HIGH
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
vuln.today AI 6.8 MEDIUM

Adjacent Bluetooth vector with AC:H reflecting the required in-window TK manipulation (AT:P equivalent); PR:N as no prior authentication is needed; no availability or scope change impact.

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

Primary rating from Vendor (Silabs).

CVSS VectorVendor: Silabs

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

DescriptionCVE.org

Passkey entry Bluetooth LE legacy pairing can be bypassed in the RS9116W and SiWx917 by manipulating the temporary key value. See vulnerability B-E3 in the related paper below.

Executive ViewAI

Why It Matters

Silicon Labs wireless modules (RS9116W, SiWx917) in WiseConnect SDK deployments contain a Bluetooth LE legacy pairing bypass that allows adjacent attackers to pair with devices without possessing the correct passkey, compromising confidentiality and integrity of connected systems. This affects all products relying on these modules for wireless connectivity. Organizations must immediately identify affected inventory and implement compensating controls, as no vendor patch currently exists.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: implementing application-layer authentication above BLE pairing, enabling detection and alerting for repeated failed pairing attempts, network segmentation to minimize exposure of affected devices, reducing Bluetooth transmission range where operationally feasible, and controlling physical access to deployment areas (adjacent proximity required for exploitation).

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Low
IoT/embedded wireless SoC, niche industrial and consumer deployments
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 HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.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
Scheduled
Exploitation
None
System Exposure· derived
Controlled
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

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

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

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