CVE-2025-7396: In wolfSSL release 5.8.2 blinding support is turned on by default for Curve25519 in applicable builds
Source GCVE Database
Not known to be exploited · CVSS 4.6 Medium · fixed in 5.8.2 : update affected systems when convenient.
Data as of 22 Nov 2026, 03:02 UTC
- Patch
- Available – fixed in 5.8.2
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
AI-suggested
wolfSSL 5.8.2 has blinding enabled by default for applicable Curve25519 builds, providing an additional layer of protection. No further action is required for users of this or later versions with the base C implementation. For builds using ARM or Intel assembly or the small Curve25519 feature, blinding is not applicable. Users should upgrade to version 5.8.2 or later to benefit from this mitigation.
Description
wolfSSL version 5.8.2 enables blinding support by default for Curve25519 in applicable builds to provide additional protection against side-channel attacks. This blinding option applies only to the base C implementation and is not available or needed for ARM or Intel assembly builds or the small Curve25519 feature. While side-channel attacks to extract private keys are difficult in practice, this mitigation adds a layer of defense for devices vulnerable to physical or side-channel observation.