CVE-2026-54872

Timing Side-Channel in Scalar Multiplication for Non-NIST EC Curves

LOW
3.7
CVSS Score
Published: September 29, 2026 at 03:32 PM UTC
Updated: October 8, 2026 at 01:19 AM UTC
1 product affected across 1 vendorOpenSSL

Using OpenSSL by OpenSSL?

Get instant alerts when new vulnerabilities affect OpenSSL - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW3.7
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.0.2 ≤ v < 1.0.2zs1.1.1 ≤ v < 1.1.1zj3.0.0 ≤ v < 3.0.233.4.0 ≤ v < 3.4.83.5.0 ≤ v < 3.5.93.6.0 ≤ v < 3.6.54.0.0 ≤ v < 4.0.31.0.21.1.13.0.03.4.03.5.03.6.04.0.0
Affected range stops below 1.0.2zs, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.1.1zj, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.23, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.6.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.3, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

3.7LOWCISA-ADP
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-208

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card