Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
3.7
Docker OpenSSL images leak signing key via timing
published 2 days ago
Summary
Docker containers that use OpenSSL for ECDSA or SM2 signatures on certain elliptic curves may expose tiny timing differences when creating signatures. An attacker who can measure many signing operations could piece together these clues to recover the private key. Use OpenSSL with the built-in NIST curves or apply patches that provide constant‑time implementations for the affected curves.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Docker Hardened Images:Debian:13 | docker hardened images | openssl | All versions |
Original advisory text
Issue summary: The generic elliptic-curve scalar multiplication used for
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.
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.
References
- https://scout.docker.com/v/DHI-7pou-hnsc-letf-xscj Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-54872 Vendor Advisory
- https://openssl-library.org/news/secadv/20260929.txt Vendor Advisory
- https://github.com/openssl/openssl/commit/8166827a78aad164a07aa86dea2b425403ced4... Patch
- https://github.com/openssl/openssl/commit/7d83bc7764999dfd91b83b4f0815b45390422a... Patch
- https://github.com/openssl/openssl/commit/3f7e1363dccec6f7732bb9e9fa471bb6e4aa68... Patch
- https://github.com/openssl/openssl/commit/1a5bee8dc57430a2be69cd1ffe7fec6a62f4f1... Patch
- https://errata.almalinux.org/9/ALSA-2026-98484.html Vendor Advisory
- https://access.redhat.com/errata/RHSA-2026:98484 Vendor Advisory
- https://security.alpinelinux.org/vuln/CVE-2026-54872 Vendor Advisory
- https://alas.aws.amazon.com/AL2/ALAS-2026-3991.html Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-84782 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-75806 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-54872 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-35189 Vendor Advisory
- https://alas.aws.amazon.com/AL2/ALAS-2026-3992.html Vendor Advisory
- https://alas.aws.amazon.com/AL2/ALAS-2026-4007.html Vendor Advisory
- https://alas.aws.amazon.com/AL2023/ALAS-2026-3204.html Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-84784 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-75805 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-75804 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-72897 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-54873 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-42772 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-35191 Vendor Advisory
- https://alas.aws.amazon.com/AL2023/ALAS-2026-3227.html Vendor Advisory
- https://security-tracker.debian.org/tracker/CVE-2026-54872 Vendor Advisory
- https://linux.oracle.com/cve/ELSA-2026-98484.html Vendor Advisory
- https://linux.oracle.com/errata/ELSA-2026-98484.html Vendor Advisory
- https://access.redhat.com/security/cve/CVE-2026-54872 Vendor Advisory
- https://www.cve.org/CVERecord?id=CVE-2026-54872 Patch
- https://errata.rockylinux.org/RLSA-2026:98484 Vendor Advisory
- https://errata.rockylinux.org/RLSA-2026:98588 Vendor Advisory
- https://ubuntu.com/security/CVE-2026-54872 Vendor Advisory
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-54872 Vendor Advisory
Internet-facing
14 days
Internal
60 days
- Not known to be exploited
- Can be exploited automatically (estimated)
- Gives an attacker partial control (estimated)
Timeline
Published20 Nov 2026
Updated20 Nov 2026
First seen20 Nov 2026
Sources
DHI-7pou-hnsc-letf-xscj · OSV
Track software like this
Free during beta