Read the docs

Infinite loop in OpenSSL CMS_encrypt() with an EC group order of 1

Priority LOW 38CWE-835Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Denial of service
Confidentiality · integrity · availability
None · None · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-835.

Summary

Affected are OpenSSL 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. Encrypting to an EC recipient certificate with group order 1 makes CMS_encrypt() or CMS_encrypt_ex() loop forever during key generation (CWE-835). An attacker who supplies the recipient certificate can exhaust a CPU core, a denial of service. Versions 4.0 and later are affected only with enable-ec_explicit_curves.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00127 2nd percentileScored 2026-11-16
Fix Fixed OpenSSL (OpenSSL): 4.1.1, 4.0.4, 3.5.10 +3

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
OpenSSLOpenSSL4.1.0 to before 4.1.1; 4.0.0 to before 4.0.4; 3.5.0 to before 3.5.10; 3.0.0 to before 3.0.24; 1.1.1 to before 1.1.1zk; 1.0.2 to before 1.0.2zt4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, 1.0.2ztPatch availableCNA
  • OpenSSL VendorOpenSSL Affected 4.1.0 to before 4.1.1; 4.0.0 to before 4.0.4; 3.5.0 to before 3.5.10; 3.0.0 to before 3.0.24; 1.1.1 to before 1.1.1zk; 1.0.2 to before 1.0.2zt Fixed in 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, 1.0.2zt Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*——OpenSSL
  • cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* Versions — — ·OpenSSL

Remediation

Upgrade OpenSSL to 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk or 1.0.2zt, depending on the branch in use.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

  • Fix · CNA OpenSSL (OpenSSL) Fixed in 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, 1.0.2zt

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Advisory ·

    OpenSSL — openssl-library.org/news/secadv/20261110.txt

    5 records Highest priority Priority LOW 5 LOW

    Other records, highest priority first

    • TI-2026-88065 Out-of-Bounds Read and Incorrect IV Length Handling in AES-GCM-SIVPriority LOW 38
    • TI-2026-88051 AES-GCM-SIV AAD forgery in OpenSSL after empty AAD updatePriority LOW 38
    • TI-2026-88064 Use-after-free in OpenSSL QUIC client via retransmitted CRYPTO framesPriority LOW 34

Timeline

  1. 2026-11-10 Threatist record created from CVE-2026-107496
  2. 2026-11-10 Alias added: GHSA-vv67-6crp-mvmp
  3. 2026-11-16 CVSS score added · CISA ADP
  4. 2026-11-16 CISA SSVC decision points changed

References

  • TI-2022-01915 The c_rehash script allows command injection CVSS 3.1CRITICAL 9.8
  • TI-2021-02645 SM2 Decryption Buffer Overflow CVSS 3.1CRITICAL 9.8
  • TI-2009-03392 The TLS protocol, and the SSL protocol 3.0 and possibly earlier, as used in Microsoft… CVSS 3.1CRITICAL 9.8
  • TI-2022-01176 The c_rehash script allows command injection CVSS 3.1CRITICAL 9.8
  • TI-2014-00154 Out-of-bounds read in OpenSSL TLS and DTLS Heartbeat handling KEVCVSS 3.1HIGH 7.5
  • TI-2025-14107 Stack buffer overflow in CMS (Auth)EnvelopedData parsing CVSS 3.1HIGH 8.8
See all 328 →

Sources