cve.bz

CVE-2026-107496 openssl openssl: Infinite Loop

no score yetEPSS 0.1%

openssl openssl: no CVSS score yet. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
Issue summary: Encrypting a CMS message to an EC certificate whose group order is 1 may cause CMS_encrypt() or CMS_encrypt_ex() to loop indefinitely. Impact summary: An attacker able to supply the recipient certificate to an application performing CMS encryption can cause that application to loop indefinitely, consuming CPU and resulting in Denial of Service. CWE: CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') Description: CMS_encrypt() and CMS_encrypt_ex() encrypt a message to one or more recipient certificates and, for an EC recipient, generate an ephemeral key in the recipient's group. If the certificate declares a group order of 1, random scalar generation can only produce zero. The key generation routine then retries without limit while waiting for a nonzero private scalar, so the call never returns. The OpenSSL TLS and QUIC implementations do not use this path. An application is exposed only if it calls CMS_encrypt() or CMS_encrypt_ex() with a recipient certificate whose EC parameters are attacker-controlled. Certificates with normal EC group orders do not trigger the loop. OpenSSL 4.0 and later reject unknown explicit EC groups in default builds. These versions are affected only when configured with the enable-ec_explicit_curves option. The result is a hang that consumes a CPU core until the process is interrupted, a Denial of Service. The severity is Low because the attacker must supply the recipient certificate and the application must choose to encrypt to it; ordinary CMS encryption to trusted recipients is unaffected. The fix makes EC key generation fail when the group has no valid nonzero private scalar, instead of retrying indefinitely. FIPS impact: no The FIPS modules in 4.1, 4.0, 3.5 and 3.0 are not affected. The FIPS provider does not support arbitrary explicit EC domain parameters, so an order-1 group is rejected during key import before the vulnerable key generation path is reached.
EPSS
0.1% estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-835 Loop with Unreachable Exit Condition (Infinite Loop)
Published
Modified
Assigned by
openssl (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-107496 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107496?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107496?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-107496 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-107496

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-107496](https://cve.bz/cve/badge/CVE-2026-107496.svg)](https://cve.bz/cve/CVE-2026-107496)

HTML:

<a href="https://cve.bz/cve/CVE-2026-107496"><img src="https://cve.bz/cve/badge/CVE-2026-107496.svg" alt="CVE-2026-107496"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
OpenSSLfrom 4.1.0 before 4.1.1
OpenSSLfrom 4.0.0 before 4.0.4
OpenSSLfrom 3.5.0 before 3.5.10
OpenSSLfrom 3.0.0 before 3.0.24
OpenSSLfrom 1.1.1 before 1.1.1zk
OpenSSLfrom 1.0.2 before 1.0.2zt

Fix and patched versions

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14opensslno fix listedDEBIAN-CVE-2026-107496
Ubuntu22.04:LTS, 24.04:LTS, Pro:20.04:LTSedk2, opensslno fix listedUBUNTU-CVE-2026-107496
Ubuntu26.04:LTS, 26.10edk2, openssl, edk2-hweno fix listedUBUNTU-CVE-2026-107496
UbuntuPro:14.04:LTS, Pro:FIPS-updates:16.04:LTS, Pro:FIPS-updates:18.04:LTS and 4 moreopensslno fix listedUBUNTU-CVE-2026-107496
UbuntuPro:16.04:LTSedk2, nodejs, opensslno fix listedUBUNTU-CVE-2026-107496
UbuntuPro:18.04:LTSedk2, nodejs, openssl and 1 moreno fix listedUBUNTU-CVE-2026-107496
UbuntuPro:22.04:LTSnodejsno fix listedUBUNTU-CVE-2026-107496
UbuntuPro:FIPS-preview:22.04:LTS, Pro:FIPS-updates:22.04:LTSopenssl, openssl-fipsno fix listedUBUNTU-CVE-2026-107496
UbuntuPro:FIPS-updates:24.04:LTSopenssl-fipsno fix listedUBUNTU-CVE-2026-107496
Alpaquita23openssl3.0.22-r2BELL-CVE-2026-107496
Alpaquita25, streamopenssl3.5.9-r1BELL-CVE-2026-107496
BellSoft Hardened Containers23openssl3.0.22-r2BELL-CVE-2026-107496
BellSoft Hardened Containers25, streamopenssl3.5.9-r1BELL-CVE-2026-107496

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita · BellSoft Hardened Containers.

References

Check your stackJSON