CVE-2026-77696
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 0.4% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.4% in the next 30 days (EPSS).
- Severity: 3.7 LOW (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.4% · EPSS, next 30 days
- Weakness
- CWE-208
- Record status
- Analyzed
Affected
- OpenSSL < 1.1.1zj
- OpenSSL < 3.0.23
- OpenSSL < 3.4.8
- OpenSSL < 3.5.9
- OpenSSL < 3.6.5
- OpenSSL < 4.0.3
Attack profile CVSS 3.1 · 3.7
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-77696.md and follow it. Check whether this project is affected by CVE-2026-77696. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/openssl/openssl/commit/1c4aed808a7aea32d2d013049c2e0d9fef164fc9
- https://github.com/openssl/openssl/commit/20b20628d39b2dcc4677194bd68c7c060fa598cb
- https://github.com/openssl/openssl/commit/419f5cb519721dceed393dbc524d79e487c72e64
- https://github.com/openssl/openssl/commit/6b90445a56b99a328ac1feba058abf976504f440
- https://openssl-library.org/news/secadv/20260929.txt
References
- https://github.com/openssl/openssl/commit/1c4aed808a7aea32d2d013049c2e0d9fef164fc9
- https://github.com/openssl/openssl/commit/20b20628d39b2dcc4677194bd68c7c060fa598cb
- https://github.com/openssl/openssl/commit/419f5cb519721dceed393dbc524d79e487c72e64
- https://github.com/openssl/openssl/commit/6b90445a56b99a328ac1feba058abf976504f440
- https://openssl-library.org/news/secadv/20260929.txt