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.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| wolfSSL | wolfSSL | 5.8.0; 0 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | wolfssl | No fix yet | — |
| Ubuntu 26.04 LTS | wolfssl | No fix yet | — |
| Ubuntu 25.10 | wolfssl | No fix yet | — |
| Ubuntu 24.04 LTS | wolfssl | No fix yet | — |
| Ubuntu 22.04 LTS | wolfssl | No fix yet | — |
Show 3 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 20.04 LTS | wolfssl | No fix yet | — |
| Ubuntu 18.04 LTS | wolfssl | No fix yet | — |
| Ubuntu 16.04 LTS | wolfssl | No fix yet | — |