# CVE-2025-11935: Forward Secrecy Violation in WolfSSL TLS 1.3


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Nov 2025
- **Updated:** 8 Dec 2025
- **Also known as:** DEBIAN-CVE-2025-11935, GHSA-4497-xvm3-5vh9, UBUNTU-CVE-2025-11935

## What is CVE-2025-11935?

CVE-2025-11935 is a medium-severity vulnerability in Wolfssl Wolfssl, published on 21 Nov 2025. 

### 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.

Weakness: CWE-326 (Inadequate Encryption Strength)

## Which versions are affected by CVE-2025-11935?

It affects 1 product.


Products: Wolfssl Wolfssl.

## How do I fix CVE-2025-11935?

No fix has been published for CVE-2025-11935 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-11935 being exploited?

There is no known exploitation of CVE-2025-11935 in the wild and no public exploit code.

## Other vulnerabilities in Wolfssl Wolfssl

- [CVE-2024-5991](https://insights.sbomify.com/CVE-2024-5991/): Buffer overread in domain name matching (critical 10.0)
- [CVE-2021-37155](https://insights.sbomify.com/CVE-2021-37155/): Security feature bypass in n/a (critical 9.8)
- [CVE-2020-36177](https://insights.sbomify.com/CVE-2020-36177/): Memory corruption in n/a (critical 9.8)
- [CVE-2014-2896](https://insights.sbomify.com/CVE-2014-2896/): Memory corruption in n/a (critical 9.8)
- [CVE-2014-2897](https://insights.sbomify.com/CVE-2014-2897/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11935 and fix it if it is affected.

What it is: CVE-2025-11935 is a medium-severity vulnerability in Wolfssl Wolfssl, published on 21 Nov 2025. 
Exploitation: There is no known exploitation of CVE-2025-11935 in the wild and no public exploit code.

Affected product: Wolfssl Wolfssl. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-11935/ (Markdown: https://insights.sbomify.com/CVE-2025-11935/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11935
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11935
- OSV: https://osv.dev/vulnerability/CVE-2025-11935

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-11935/
Summaries are generated and may contain mistakes; the official description above is the record.