# CVE-2025-7396: Curve25519 Blinding

> Enabling Curve25519 blinding in wolfSSL mitigates potential side-channel attacks that could expose private keys.

- **Severity:** Medium 5.6 (`CVSS:4.0/AV:P/AC:H/AT:P/PR:L/UI:A/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Jul 2025
- **Updated:** 21 Jul 2025
- **Also known as:** GHSA-h9v3-wvxh-4mwp, UBUNTU-CVE-2025-7396

## What is CVE-2025-7396?

CVE-2025-7396 is a medium-severity vulnerability in Wolfssl Wolfssl, published on 18 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In wolfSSL release 5.8.2 blinding support is turned on by default for Curve25519 in applicable builds. The blinding configure option is only for the base C implementation of Curve25519. It is not needed, or available with; ARM assembly builds, Intel assembly builds, and the small Curve25519 feature. While the side-channel attack on extracting a private key would be very difficult to execute in practice, enabling blinding provides an additional layer of protection for devices that may be more susceptible to physical access or side-channel observation.

Weakness: CWE-385 (Covert Timing Channel)

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

It affects 1 product.


Products: Wolfssl Wolfssl.

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

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

## Is CVE-2025-7396 being exploited?

There is no known exploitation of CVE-2025-7396 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-7396 and fix it if it is affected.

What it is: CVE-2025-7396 is a medium-severity vulnerability in Wolfssl Wolfssl, published on 18 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-7396 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-7396/ (Markdown: https://insights.sbomify.com/CVE-2025-7396/index.md)
```

## Sources

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

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