BLE impersonation via re-pairing key-size downgrade
Published Aug 13, 2026 · Updated Aug 13, 2026
Authentication downgrade in WiSeConnect SDK 2.0.0 through 2.13.1 and 4.0.0 through 4.0.3 allows physically proximate attackers to weaken BLE keys. The BLE re-pairing path accepts a lower security level than the existing bond because it does not enforce a minimum SMP encryption key size. Without credentials, physically proximate attackers can force re-pairing, brute-force the shortened LTK, and impersonate a paired device or intercept its traffic.
Summary
What happened
Authentication downgrade in WiSeConnect SDK 2.0.0 through 2.13.1 and 4.0.0 through 4.0.3 allows physically proximate attackers to weaken BLE keys. The BLE re-pairing path accepts a lower security level than the existing bond because it does not enforce a minimum SMP encryption key size. Without credentials, physically proximate attackers can force re-pairing, brute-force the shortened LTK, and impersonate a paired device or intercept its traffic.
The record
- CVE
- CVE-2026-19292
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- Sigma Designs
- Product
- WiSeConnect SDK
- Classifications
- CWE-305, CAPEC-180, T1557
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 13, 2026CVE publishedPublication date reported by the CVE source.
- Aug 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0 <2.14.0
- Affected versionversion=4.0.0 <4.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- BLERP research toolkitfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo