Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
3.7

Docker OpenSSL images may leak SM2 keys via timing

published 2 days ago
Summary

Docker images that include OpenSSL’s SM2 signing function can reveal secret values by how long a signature takes to compute. An attacker who can measure those times could eventually recover the private key. Update OpenSSL to a version that uses constant‑time operations or avoid using SM2 in these images.

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 VendorProductAffected versions
Docker Hardened Images:Debian:13 docker hardened images openssl All versions
Original advisory text
Issue summary: SM2 signature generation uses non-constant-time arithmetic
Issue summary: SM2 signature generation uses non-constant-time arithmetic
on secret values, forming a timing side-channel.

Impact summary: An attacker able to measure SM2 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: SM2 signature generation computes the signature value using
variable-time BIGNUM operations on the secret nonce and the private key, so
the time taken to produce an SM2 signature depends on these secret values,
forming a timing side-channel.

Applications performing SM2 signature generation are affected on all
platforms.

FIPS Impact: no
SM2 is not a FIPS algorithm.
Fix within
Internet-facing 14 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically (estimated)
  • Gives an attacker partial control (estimated)
Severity
3.7 Low
Timeline
Published20 Nov 2026
Updated20 Nov 2026
First seen20 Nov 2026
Sources
Track software like this
Free during beta