How severe is CVE-2025-7396?

CVE-2025-7396 has a CVSS 3.x base score of 4.6, rated medium severity. It is exploitable over physical access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2025-7396 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (8th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-7396?

CVE-2025-7396 affects Wolfssl. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-7396?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-7396 have an EU (EUVD) identifier?

Yes. CVE-2025-7396 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-21941.

When was CVE-2025-7396 published?

CVE-2025-7396 was published on 2025-07-18 and last updated on 2026-06-17.

CVE-2025-7396

CVE-2025-7396 is a medium-severity vulnerability in Wolfssl with a CVSS 3.x base score of 4.6. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-385.

Key facts

Severity: Medium (CVSS 3.x base score 4.6)
CVSS v4: 5.6
EPSS exploit prediction: 0% (8th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-21941
Weakness: CWE-385
Affected product: Wolfssl
Published: 2025-07-18
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2025-7396?: 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.
How severe is CVE-2025-7396?: CVE-2025-7396 has a CVSS 3.x base score of 4.6, rated medium severity. It is exploitable over physical access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2025-7396 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (8th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-7396?: CVE-2025-7396 affects Wolfssl. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-7396?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-7396 have an EU (EUVD) identifier?: Yes. CVE-2025-7396 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-21941.
When was CVE-2025-7396 published?: CVE-2025-7396 was published on 2025-07-18 and last updated on 2026-06-17.

References

https://github.com/wolfSSL/wolfssl/blob/master/ChangeLog.md#wolfssl-release-582-july-17-2025

Affected products (1)

cpe:2.3:a:wolfssl:wolfssl:5.8.2:*:*:*:*:*:*:*

More vulnerabilities in Wolfssl

CVE-2026-7531 — Critical (CVSS 9.8): Use-after-free in PQC hybrid key-share handling. This is an incomplete-fix follow-up to CVE-2026-5460 (released in…
CVE-2026-5264 — Critical (CVSS 9.8): Heap buffer overflow in DTLS 1.3 ACK message processing. A remote attacker can send a crafted DTLS 1.3 ACK message that…
CVE-2026-5187 — Critical (CVSS 9.8): Two potential heap out-of-bounds write locations existed in DecodeObjectId() in wolfcrypt/src/asn.c. First, a bounds…
CVE-2026-4395 — Critical (CVSS 9.8): Heap-based buffer overflow in the KCAPI ECC code path of wc_ecc_import_x963_ex() in wolfSSL wolfcrypt allows a remote…
CVE-2026-3849 — Critical (CVSS 9.8): Stack Buffer Overflow in wc_HpkeLabeledExtract via Oversized ECH Config. A vulnerability existed in wolfSSL 5.8.4 ECH…
CVE-2026-3549 — Critical (CVSS 9.8): Heap Overflow in TLS 1.3 ECH parsing. An integer underflow existed in ECH extension parsing logic when calculating a…

All CVEs affecting Wolfssl →

Other CWE-385 vulnerabilities

CVE-2026-5598 — High (CVSS 7.5): Covert timing channel vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA core on all (core modules). This…
CVE-2025-59425 — High (CVSS 7.5): vLLM is an inference and serving engine for large language models (LLMs). Before version 0.11.0rc2, the API key support…
CVE-2020-25658 — High (CVSS 7.5): It was found that python-rsa is vulnerable to Bleichenbacher timing attacks. An attacker can use this flaw via the RSA…
CVE-2025-0306 — High (CVSS 7.4): A vulnerability was found in Ruby. The Ruby interpreter is vulnerable to the Marvin Attack. This attack allows the…
CVE-2023-46809 — High (CVSS 7.4): Node.js versions which bundle an unpatched version of OpenSSL or run against a dynamically linked version of OpenSSL…
CVE-2023-3640 — High (CVSS 7.0): A possible unauthorized memory access flaw was found in the Linux kernel's cpu_entry_area mapping of X86 CPU data to…

Browse all CWE-385 vulnerabilities →