UBUNTU-CVE-2026-107496: Medium severity ubuntu/openssl vulnerability

Published Nov 12, 2026
·
Updated

Issue summary: Encrypting a CMS message to an EC certificate whose group order is 1 may cause CMSencrypt() or CMSencryptex() 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: CMSencrypt() and CMSencryptex() 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 CMSencrypt() or CMSencryptex() 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-ecexplicitcurves 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.

Affected Software

32 affected components
ubuntu/openssl*
ubuntu/openssl*
ubuntu/edk2*
ubuntu/nodejs*
ubuntu/openssl*
ubuntu/openssl*
ubuntu/openssl*
ubuntu/openssl1.0*
ubuntu/edk2*
ubuntu/nodejs*
ubuntu/openssl*
ubuntu/openssl*
ubuntu/edk2*
ubuntu/openssl*
ubuntu/openssl*
ubuntu/openssl*
ubuntu/edk2*
ubuntu/openssl*
ubuntu/nodejs*
ubuntu/openssl*
ubuntu/openssl-fips*
ubuntu/openssl*
ubuntu/openssl-fips*
ubuntu/edk2*
ubuntu/openssl*
ubuntu/openssl-fips*
ubuntu/edk2*
ubuntu/edk2-hwe*
ubuntu/openssl*
ubuntu/edk2*
ubuntu/edk2-hwe*
ubuntu/openssl*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Disable the enable-ec_explicit_curves option; the affected versions are vulnerable only when configured with this option.

    OpenSSL enable-ec_explicit_curves = disabled

Event History

Nov 12, 2026
CVE Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Are OpenSSL TLS or QUIC deployments affected by this issue?

No. The OpenSSL TLS and QUIC implementations do not use the affected CMS encryption path.

2

What must an attacker control to trigger the denial of service?

The application must call CMS_encrypt() or CMS_encrypt_ex() and use a recipient certificate with attacker-controlled EC parameters. A certificate declaring an EC group order of 1 can cause the operation to consume CPU indefinitely.

3

Does this affect applications using ordinary EC recipient certificates?

No. Certificates with normal EC group orders do not trigger the loop. Exposure is limited to CMS encryption using a recipient certificate with the malformed EC group parameters.

4

Do newer OpenSSL default builds provide any protection?

OpenSSL 4.0 and later reject unknown explicit EC groups in default builds. The provided information does not establish that this protection covers every possible affected certificate configuration.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203