wolfSSL: Inadequate Encryption Strength
CVE-2025-11935 is a high-severity inadequate encryption strength vulnerability in wolfSSL, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 5.8.4 as the first without the flaw, so updating wolfSSL to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.23% 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 wolfSSL to 5.8.4 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
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
- NetworkCan be exploited remotely over a network, including the internet.
- 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
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 6.3 | Medium | CNA (wolfssl.com) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
With TLS 1.3 pre-shared key (PSK) a malicious or faulty server could ignore the request for PFS (perfect forward secrecy) and the client would continue on with the connection using PSK without PFS. This happened when a server responded to a ClientHello containing psk_dhe_ke without a key_share extension. The re-use of an authenticated PSK connection that on the clients side unexpectedly did not have PFS, reduces the security of the connection.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Inadequate Encryption Strength
The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.
How developers prevent this class of flaw
- Use an encryption scheme that is currently considered to be strong by experts in the field.
More Inadequate Encryption Strength vulnerabilities (CWE-326)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/wolfSSL/wolfssl/pull/9112Issue Tracking
Other references
- github.com/wolfSSL/wolfsslProduct
Other vulnerabilities in wolfSSL
- 8.2 High severity
- 8.3 High severity
- 9.1 Critical severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Recent Inadequate Encryption Strength vulnerabilities
- 8.7 High severity
- 7.0 High severity
- 8.2 High severity
- 7.5 High severity
- 7.5 High severity
- 7.3 High severity
Spotted an error? Tell us.