Is CVE-2026-54872 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-54872 being exploited in the wild.

How severe is CVE-2026-54872?

Informational severity, published 29 September 2026.

Is there a fix for CVE-2026-54872?

A patch was published on 2026-09-29. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-54872 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-54872?

Check whether you run OpenSSL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-54872: OpenSSL elliptic-curve scalar multiplication timing leak in ECDSA and SM2

CVE-2026-54872 · Severity: info · Published 2026-09-29

OpenSSL's generic elliptic-curve scalar multiplication implementation used for ECDSA and SM2 digital signatures leaks timing information about the secret nonce. An attacker who can measure the duration of many signing operations may recover the private signing key through statistical analysis, compromising the confidentiality of digitally signed transactions and communications.

Technologies: OpenSSL. Vendors: OpenSSL.

Quick answers

Is CVE-2026-54872 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-54872 being exploited in the wild.
How severe is CVE-2026-54872?: Informational severity, published 29 September 2026.
Which products and versions are affected?: OpenSSL 3.x before fix.
Is there a fix for CVE-2026-54872?: A patch was published on 2026-09-29. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-54872 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-54872?: Check whether you run OpenSSL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a timing side-channel in the generic scalar multiplication code path used for elliptic curves without dedicated constant-time implementations (e.g., Brainpool curves). The BIGNUM padding operations are not constant-time, allowing nonce value inference through timing measurements. NIST curves P-256, P-384, and P-521 are unaffected due to their dedicated constant-time implementations.

Affected products

OpenSSL OpenSSL 3.x before fix

Timeline

2026-09-29: disclosed
2026-09-29: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.