Bug 2578176 - CVE-2026-107496 erlang: openssl: Denial of Service via crafted EC certificate in CMS encryption [fedora-all]
Summary: CVE-2026-107496 erlang: openssl: Denial of Service via crafted EC certificate...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: erlang
Version: rawhide
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["559b6021-b7f4-45d5-9f43-3...
Depends On:
Blocks: CVE-2026-107496
TreeView+ depends on / blocked
 
Reported: 2026-11-20 12:38 UTC by Srikanth Balasubramanian
Modified: 2026-11-20 14:25 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-11-20 14:25:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Srikanth Balasubramanian 2026-11-20 12:38:44 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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.

Comment 1 Peter Lemenkov 2026-11-20 14:25:46 UTC
erlang is not affected by CVE-2026-107496.

This flaw is in OpenSSL's CMS encryption handling with EC certificates (denial of service via a crafted EC certificate). Erlang/OTP neither ships nor exercises that code:

- The crypto and ssl applications link against the *system* OpenSSL (BuildRequires: pkgconfig(openssl)); any fix for CVE-2026-107496 is delivered by the openssl package.
- Erlang's crypto application calls the system libcrypto for these operations and carries no copy of the CMS or elliptic-curve code.
- The only OpenSSL code *bundled* in OTP (Provides: bundled(openssl) = 3.1.4) is a very small part of the MD5 digest — erts/emulator/openssl/ holds only crypto/md5/md5_dgst.c, crypto/md5/md5_local.h, include/crypto/md32_common.h and include/openssl_local/md5.h (see erts/emulator/openssl/README). No CMS or elliptic-curve code is bundled.

The vulnerable code path therefore does not exist in Erlang/OTP. Closing as NOTABUG (not affected).


Note You need to log in before you can comment on or make changes to this bug.