Koffei

CVE-2026-77696

🟡 Low

OpenSSL · 4.0.0-<4.0.3; 3.6.0-<3.6.5; 3.5.0-<3.5.9; 3.4.0-<3.4.8; 3.0.0-<3.0.23; 1.1.1-<1.1.1zj

CVSS (Koffei note)
3.7
CVSS (v3.1, CVE List)
3.7
EPSS (2026-11-18)
0.454%
40.08th percentile

Exploitation

No (SSVC: none, CISA-ADP 2026-09-29); not in KEV. Not in the 0day "In the Wild" sheet (checked 18/11/2026). cyberveille RSS: checked 18/11/2026 (feed 19/10 to 17/11/2026), no result (automated enrichment)

Timeline

  1. 29/09/2026CVE record published (CVE List)
  2. 18/11/2026CERT-FR relays Oracle's off-cycle November update for six product lines

Risk

3.7 Low (v3.1, CISA-ADP) — AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N, EPSS 0.454%, 39.98th percentile, scored 2026-11-17 (CWE-208: SM2 signature generation uses non-constant-time arithmetic on the secret nonce and private key; timing measurements over many signatures could allow lattice-based private key recovery. Not a FIPS algorithm.)

Fix

Yes — Oracle Database Server: Oracle cspunov2026 (17/11/2026) ; component fix per record: 4.0.3, 3.6.5, 3.5.9, 3.4.8, 3.0.23, 1.1.1zj

Official description

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.

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

CWE-208