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

OpenSSL on ARM64/RISC-V may leak private key info

published 24 days ago
Summary

OpenSSL versions 4.0, 3.6, 3.5 and 3.4 on ARM64 and RISC‑V processors use a speed‑optimized calculation that can reveal bits of a private key or signing secret through timing or cache observations. An attacker who can measure how long operations take could potentially recover secret information. Update OpenSSL to the latest patched versions (4.0.3, 3.6.5, 3.5.9 or 3.4.8) to close the gap.

What to do
  • Update openeuler openssl to version 3.0.12-55.oe2403sp1.
Affected software
Ecosystem VendorProductAffected versions
openEuler:24.03-LTS-SP1 openeuler openssl < 3.0.12-55.oe2403sp1
Fix: upgrade to 3.0.12-55.oe2403sp1
Original advisory text
openssl security update
OpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.

Security Fix(es):

Issue summary: A non-constant-time optimized implementation of scalar
point multiplication is used for SM2 private key operations on ARM64 and
RISC-V platforms.

Impact summary: An attacker able to measure the time taken by, or to observe
the cache-line access pattern of SM2 signing or decryption on an affected
platform can learn information about the secret scalar.

CWE: CWE-208: Observable Timing Discrepancy

Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized
scalar multiplication implementation whose conditional branches and table
look ups are chosen according to the bits of the secret scalar. The execution
time and the cache-access pattern therefore depend on the long-term private
key (during SM2 decryption) or the per-signature nonce (during SM2 signature
generation), forming a timing and cache side-channel.

FIPS Impact: no
SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part
of the FIPS module.

OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and
RISC-V.

OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.

OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3.
OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5.
OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9.
OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8.

This issue was reported on 2 May 2026 by Abhinav Agarwal.
It was independently reported on 6 June 2026 by Feng Xue.
The fix was developed by Igor Ustinov.

-- cut (non-publishing metadata for internal use) --
Reported by: Abhinav Agarwal, Feng Xue
Fixed by: Igor Ustinov(CVE-2026-54875)
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
Published29 Oct 2026
Updated29 Oct 2026
First seen29 Oct 2026
Sources
Track software like this
Free during beta