WiseConnect: Weak Password Requirements
CVE-2026-19293 is a high-severity weak password requirements vulnerability in WiseConnect from Silabs.com, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists versions 4.1.0, 2.14.0 as the first without the flaw, so updating WiseConnect to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.2% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update WiseConnect to 4.1.0 or 2.14.0, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Silabs.com | WiseConnect | 4.0.0 up to, but not including, 4.1.0; 2.0.0 up to, but not including, 2.14.0 | 4.1.0, 2.14.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (silabs.com).
Official description
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-forcing the key easier. See V6 in BLERP paper linked below.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Weak Password Requirements
The product does not require that users should have strong passwords.
How developers prevent this class of flaw
- Consider a second authentication factor beyond the password, which prevents the password from being a single point of failure. See CWE-308 for further information.
- Consider implementing a password complexity meter to inform users when a chosen password meets the required attributes.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
Other vulnerabilities in WiseConnect
- 7.6 High severity
- 8.8 High severity
Recent Weak Password Requirements vulnerabilities
- 9.8 Critical severity
- 8.8 High severity
- 9.1 Critical severity
- 8.1 High severity
- 9.8 Critical severity
- 9.1 Critical severity
Spotted an error? Tell us.