Skip to main content

Silicon Labs WiseConnect CVE-2026-19291

| EUVDEUVD-2026-57926 HIGH
Authentication Bypass by Spoofing (CWE-290)
2026-08-13 Silabs GHSA-8pg2-cp78-vjmv
8.8
CVSS 3.1 · Vendor: Silabs
View

Attack ChainAIDerived

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

  1. Access
    Position within Bluetooth range
  2. Delivery
    Identify device with existing BLE bond
  3. Exploit
    Initiate re-pairing request to target
  4. Execution
    Negotiate lower security level during pairing exchange
  5. Persist
    Establish downgraded security association
  6. Impact
    Intercept or inject BLE communications

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Anti-spoofing controls
MITRE ATT&CK

1 technique across 1 tactic: Defense Evasion

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The target device must be a Silicon Labs RS9116W or SiWx91x running WiseConnect firmware prior to the fixed versions (2.14.0 or 4.1.0). An existing BLE bond or pairing relationship must exist between the target device and a legitimate peer - the vulnerability is specifically triggered during re-pairing with a known bonded device, not initial pairing. The attacker must be within Bluetooth radio range (adjacent network vector, AV:A). The CVSS vector PR:N indicates no attacker-side authentication is required. Exploitation is limited by physical proximity to the target device; internet-remote exploitation is not possible. No specific non-default configuration is required beyond the device having an established BLE bond.

Impact

The NVD CVSS 3.1 score of 8.8 with vector AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H reflects a severe but proximity-constrained threat: the attacker must be within Bluetooth radio range (typically 10-100 meters depending on device class), which meaningfully limits the attack surface compared to internet-reachable vulnerabilities. No EPSS score was provided in the input data, so probability cannot be quantified numerically. KEV status is not confirmed, meaning mass active exploitation is not currently evidenced. However, the NDSS-published BLERP paper represents credible, peer-reviewed proof-of-concept research, which substantially lowers the bar for adversary replication. The combination of PR:N (no attacker authentication), AC:L (no complex precondition beyond radio proximity), and full C/H/I:H/A:H impact makes this a genuine operational priority for deployments of WiseConnect-based devices in sensitive or physically accessible environments. The primary limiting factor is the adjacency requirement - this is not remotely exploitable over the internet.

Exploit ScenarioDerived

An attacker within Bluetooth range of a WiseConnect-based device that has an existing bond with a legitimate peer initiates a re-pairing exchange, negotiating a weaker security mode (e.g., unauthenticated Just Works instead of the original MITM-protected mode) that the vulnerable stack accepts without enforcement. The NDSS BLERP paper documents this as a reproducible V3 attack variant, indicating a working research prototype exists. With the downgraded security association in place, the attacker can intercept or inject BLE traffic, impersonate the bonded peer, or disrupt device operation.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 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 Low Energy re-pairing in Silicon Labs RS9116W and SiWx91x devices allows a nearby unauthenticated attacker to negotiate a lower security level during the re-pairing process with an already-bonded peer, effectively bypassing the previously established security guarantees. Documented as the 'V3' attack variant in the NDSS-published BLERP (BLE Re-Pairing) research paper, this flaw enables high-impact compromise of confidentiality, integrity, and availability across affected WiseConnect firmware lines. No public exploit code or CISA KEV listing is confirmed at time of analysis, though the NDSS publication constitutes academic proof-of-concept disclosure.

RemediationAI

Upgrade WiseConnect 2.x deployments to version 2.14.0 or later, and WiseConnect 4.x deployments to version 4.1.0 or later, per the vendor advisory at https://community.silabs.com/068Vm00000x0yyH. These are the earliest fixed versions per EUVD-2026-57926. If immediate firmware update is not operationally feasible, restrict physical access to environments where affected devices are deployed to reduce Bluetooth adjacency exposure - for example, deploying RF shielding in sensitive enclosures or disabling BLE functionality at the application layer if unused. Note that disabling BLE may impact product functionality depending on the device's use case. Developers integrating WiseConnect into products should re-validate all device-to-device pairing flows post-upgrade to confirm security-level enforcement is maintained during re-bonding events.

Affected VersionsENISA

WiseConnect 4.0.0 <4.1.0
WiseConnect 2.0.0 <2.14.0

Affected Packages

euvd wiseconnect fix: 2.14.0, 4.1.0

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 vulnerability resides in the Bluetooth Low Energy pairing and bonding implementation within Silicon Labs' WiseConnect SDK, which drives the RS9116W (a legacy Wi-Fi/BT combo module) and SiWx91x (next-generation wireless SoC) chipsets. CPE cpe:2.3:a:silabs.com:wiseconnect:*:*:*:*:*:*:*:* covers both affected firmware branches. CWE-290 (Authentication Bypass by Spoofing) maps to the root cause: the BLE stack fails to enforce that a re-pairing event with a known bonded device must maintain or exceed the original negotiated security level (e.g., MITM-protected Just Works vs. Passkey Entry). The BLERP paper (NDSS Symposium) systematically characterizes multiple BLE re-pairing attack classes; V3 specifically targets this security-level downgrade during rebonding, exploiting the absence of a minimum-security-level enforcement check in the host controller interface or security manager protocol layer.

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 8.8 HIGH
AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

AV:A reflects Bluetooth adjacency requirement; PR:N because attacker initiates re-pairing without credentials; AC:L as no complex conditions beyond proximity and an existing bond.

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

Primary rating from Vendor (Silabs).

CVSS VectorVendor: Silabs

Attack Vector
Adjacent
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Aug 13, 2026 - 15:02 EUVD
CVE Published
Aug 13, 2026 - 14:16 cve.org
HIGH 8.8

DescriptionCVE.org

Bluetooth re-pairing with an existing device can use a lower security level. RS9116W and SiWx91x impacted. See V3 in the BLERP paper linked below.

Executive ViewAI

Why It Matters

Silicon Labs Bluetooth devices (RS9116W and SiWx91x) running affected WiseConnect firmware contain a vulnerability allowing nearby attackers to downgrade security protections during device re-pairing, potentially compromising the confidentiality and integrity of wirelessly connected systems. This vulnerability is particularly concerning for organizations deploying these components in IoT, medical devices, or other security-sensitive environments where loss of encryption is unacceptable. Immediate patching is required to restore security guarantees and prevent unauthorized access to sensitive data.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 88% exploitable
Prevalence
Medium
widely-used IoT/embedded Bluetooth chipset across consumer and industrial products
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 Yes
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

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
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