Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and… (CVE-2026-54875)
A timing and cache side-channel vulnerability exists in the SM2 private key operations on ARM64 and RISC-V platforms in OpenSSL versions 4.0, 3.6, 3.5, and 3.4. The scalar point multiplication implementation is not constant-time, allowing attackers who can measure timing or cache access patterns during SM2 signing or decryption to potentially gain information about secret scalars. This issue does not affect OpenSSL versions 3.0, 1.1.1, or 1.0.2. Fixes have been released in OpenSSL 4.0.3, 3.6.5, 3.5.9, and 3.4.8.
AI Analysis
Technical Summary
The vulnerability (CVE-2026-54875) arises from a non-constant-time optimized scalar multiplication implementation used for SM2 private key operations on ARM64 and RISC-V processors. The implementation uses conditional branches and table lookups dependent on bits of the secret scalar, causing execution time and cache access patterns to leak information about the secret scalar during SM2 decryption or signature generation. This timing and cache side-channel can be exploited by attackers able to measure these characteristics. The issue affects OpenSSL versions 4.0, 3.6, 3.5, and 3.4 on the specified platforms, but not earlier versions 3.0, 1.1.1, or 1.0.2. Vendor fixes are available in the respective minor version updates.
Potential Impact
An attacker capable of measuring timing or observing cache-line access patterns during SM2 signing or decryption on affected ARM64 or RISC-V platforms may gain partial information about the secret scalar used in the cryptographic operations. This could weaken the confidentiality of the private key or per-signature nonce. The impact is limited to information disclosure with no direct integrity or availability effects. The vulnerability does not affect FIPS modules as SM2 is not a FIPS algorithm.
Mitigation Recommendations
Upgrading to the fixed OpenSSL versions is the recommended remediation: OpenSSL 4.0.3, 3.6.5, 3.5.9, or 3.4.8. Users of OpenSSL 4.0, 3.6, 3.5, and 3.4 on ARM64 or RISC-V platforms should apply these updates to mitigate the timing and cache side-channel vulnerability in SM2 private key operations. No other mitigations are specified by the vendor.
Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and… (CVE-2026-54875)
Description
A timing and cache side-channel vulnerability exists in the SM2 private key operations on ARM64 and RISC-V platforms in OpenSSL versions 4.0, 3.6, 3.5, and 3.4. The scalar point multiplication implementation is not constant-time, allowing attackers who can measure timing or cache access patterns during SM2 signing or decryption to potentially gain information about secret scalars. This issue does not affect OpenSSL versions 3.0, 1.1.1, or 1.0.2. Fixes have been released in OpenSSL 4.0.3, 3.6.5, 3.5.9, and 3.4.8.
CVSS v3.1
Score 3.7low
Affected software
pkg:github/openssl/opensslRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability (CVE-2026-54875) arises from a non-constant-time optimized scalar multiplication implementation used for SM2 private key operations on ARM64 and RISC-V processors. The implementation uses conditional branches and table lookups dependent on bits of the secret scalar, causing execution time and cache access patterns to leak information about the secret scalar during SM2 decryption or signature generation. This timing and cache side-channel can be exploited by attackers able to measure these characteristics. The issue affects OpenSSL versions 4.0, 3.6, 3.5, and 3.4 on the specified platforms, but not earlier versions 3.0, 1.1.1, or 1.0.2. Vendor fixes are available in the respective minor version updates.
Potential Impact
An attacker capable of measuring timing or observing cache-line access patterns during SM2 signing or decryption on affected ARM64 or RISC-V platforms may gain partial information about the secret scalar used in the cryptographic operations. This could weaken the confidentiality of the private key or per-signature nonce. The impact is limited to information disclosure with no direct integrity or availability effects. The vulnerability does not affect FIPS modules as SM2 is not a FIPS algorithm.
Mitigation Recommendations
Upgrading to the fixed OpenSSL versions is the recommended remediation: OpenSSL 4.0.3, 3.6.5, 3.5.9, or 3.4.8. Users of OpenSSL 4.0, 3.6, 3.5, and 3.4 on ARM64 or RISC-V platforms should apply these updates to mitigate the timing and cache side-channel vulnerability in SM2 private key operations. No other mitigations are specified by the vendor.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-q4gq-r6f8-q6q9
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-54875"]
- Database Specific Severity
- LOW
- Cvss Version
- 3.1
Threat ID: 6abc27c3680226ef6846f824
Added to database: 09/29/2026, 21:04:03 UTC
Last enriched: 09/29/2026, 21:19:00 UTC
Last updated: 09/30/2026, 03:16:02 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.