Silabs.com Wiseconnect
7 CVEs affecting Silabs.com Wiseconnect. Latest disclosed: 2026-08-13. Critical: 0, High: 4.
| CVE | Severity | Score | Published | Summary |
|---|---|---|---|---|
CVE-2026-19293 | High | 8.8 | 2026-08-13 | SMP security request (from peripheral) does not include the maximum encryption key size supported. Using a key with less than the maximum keysize makes brute-f… |
CVE-2026-19292 | High | 8.8 | 2026-08-13 | Re-pairing with a legitimate device can use a lower security level than previous making brute-forcing the LTK easier. See V4 in the BLERP paper linked below. |
CVE-2026-19291 | High | 8.8 | 2026-08-13 | 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. |
CVE-2026-16101 | High | 8.8 | 2026-08-13 | Spoofing an already bonded device can force either RS9116W or SiWx917 to re-pair/bond with a rogue device. See V1 in BLERP paper below |
CVE-2026-65936 | | 2026-08-13 | A malformed Bluetooth connection request message can cause the RS9116W/SiWx917 to leak potentially sensitive information. See vulnerability B-E4 in the relate… | |
CVE-2026-65935 | | 2026-08-13 | 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 re… | |
CVE-2025-3873 | | 2025-07-25 | The following APIs for the Silcon Labs SiWx91x prior to vesion 3.4.0 failed to check the size of the output buffer of the caller which could lead to data corru… |