CVE-2026-54875
Last modified
CVE-2026-54875 is a low-severity vulnerability rated 3.7/10 on the CVSS scale. 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. EPSS estimates a 0.29% chance of exploitation in the next 30 days.
Description
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
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Openssl | Openssl | >= 3.4.0, < 3.4.8 |
| Openssl | Openssl | >= 3.5.0, < 3.5.9 |
| Openssl | Openssl | >= 3.6.0, < 3.6.5 |
| Openssl | Openssl | >= 4.0.0, < 4.0.3 |
References
- https://openssl-library.org/news/secadv/20260929.txtVendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-54875?
How severe is CVE-2026-54875?
How do I fix CVE-2026-54875?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-5487DriveLock Directory Traversal Information Disclosure Vulnera…7.5
- CVE-2026-54870Improper Neutralization of Input During Web Page Generation …6.5
- CVE-2026-54871Missing Authorization vulnerability in Mamunur Rashid ShopBu…5.3
- CVE-2026-54872Issue summary: The generic elliptic-curve scalar multiplicat…3.7
- CVE-2026-54873Issue summary: QUIC process may keep memory for QUIC packet …7.5
- CVE-2026-54874Issue summary: Receiving a DTLS record for a future epoch wh…7.5
- CVE-2026-54876Issue summary: A malicious TLS server can cause a memory lea…7.5
- CVE-2026-5488The ExactMetrics – Google Analytics Dashboard for WordPress …5.3
- CVE-2026-54885Server-Side Request Forgery vulnerability in malach-it Borut…6.9
- CVE-2026-54886Loop with Unreachable Exit Condition ('Infinite Loop') vulne…4.3
- CVE-2026-54887Use of Default Cryptographic Key vulnerability in Erlang/OTP…4.8
- CVE-2026-54888Uncontrolled Recursion vulnerability in leandrocp mdex allow…6.9
Are you affected by CVE-2026-54875?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
