CVE-2026-107496: OpenSSL CMS Encryption Infinite Loop with Order-1 EC Recipient Certificates
CVE-2026-107496 is an infinite-loop vulnerability in OpenSSL CMS encryption. When CMS_encrypt() or CMS_encrypt_ex() encrypts to an elliptic-curve recipient certificate declaring a group order of 1, ephemeral-key generation can produce only zero-valued private scalars. The key-generation routine retries indefinitely while waiting for a nonzero scalar, preventing the encryption call from returning and causing denial of service. Affected release ranges are 4.1.0 before 4.1.1, 4.0.0 before 4.0.4, 3.5.0 before 3.5.10, 3.0.0 before 3.0.24, 1.1.1 before 1.1.1zk, and 1.0.2 before 1.0.2zt. OpenSSL 4.0 and later are exposed only when built with enable-ec_explicit_curves. OpenSSL TLS and QUIC implementations do not use the vulnerable path.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation hangs the affected CMS encryption operation indefinitely and consumes a CPU core until the process is interrupted, causing application denial of service. The identified impact is limited to availability; no confidentiality or integrity compromise is established. OpenSSL rates the issue Low because an attacker must supply a recipient certificate that the application chooses to use for encryption. Ordinary encryption to trusted recipients with normal EC group orders is unaffected. The OpenSSL FIPS modules in the 4.1, 4.0, 3.5, and 3.0 branches are unaffected because arbitrary explicit EC parameters are rejected during key import.
Mitigation
If you can’t patch tonight, do this now.
Restrict CMS encryption to trusted recipient certificates with normal EC group orders, and reject attacker-controlled explicit EC parameters, particularly groups declaring order 1. For OpenSSL 4.0 and later, use default builds without enable-ec_explicit_curves so unknown explicit EC groups are rejected. Interrupt an affected process to stop an active CPU-consuming hang; this does not correct the vulnerability.
Remediation
Patch, then assume compromise.
Apply the OpenSSL patch that makes EC key generation fail when a group has no valid nonzero private scalar, rather than retrying indefinitely. The designated fixed releases are 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, and 1.0.2zt for their respective branches. Fixes have been committed to the public repository, with releases scheduled for December 1, 2026; apply the appropriate patch before then if a fixed package is unavailable. Access to fixes for legacy branches may require premium support.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-107496 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-107496 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-107496?
- As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-107496.
- Is there a patch for CVE-2026-107496?
- Apply the OpenSSL patch that makes EC key generation fail when a group has no valid nonzero private scalar, rather than retrying indefinitely. The designated fixed releases are 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, and 1.0.2zt for their respective branches.
- How severe is CVE-2026-107496?
- CVE-2026-107496 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.13% (2nd percentile) as of Nov 17, 2026.
Recent activity
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.