Bug 2574245 (CVE-2026-107493)

Summary: CVE-2026-107493 openssl: openssl: Denial of Service via malformed PEM data in PEM_X509_INFO_read_bio_ex
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: abarbaro, akhatavk, alizardo, aos-team-art-private, asdas, csutherl, dpaolell, ehelms, jchui, jclere, jdelft, jhe, jpasqual, jupierce, juwatts, ktsao, lblicha, lgarciaa, mbiarnes, mhulan, nboldt, oaljalju, ogajduse, osousa, pjindal, plodge, ppalepu, ppostler, prdhamdh, psrna, rchan, rhel-process-autobot, sghai, sidsharm, smallamp, suppawar, szappis, vchlup, vlaad, watson-tool-maintainers, zhunting
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in OpenSSL. When an application provides an existing stack of certificate structures to PEM parsing functions, such as PEM_X509_INFO_read_bio_ex(), and the read operation fails, OpenSSL deallocates all entries in the stack while retaining pointers to the freed memory. A remote attacker can supply malformed Privacy-Enhanced Mail (PEM) data to trigger a read failure. If the calling application subsequently accesses or frees the affected stack, it can cause memory corruption or an application crash resulting in a Denial of Service (DoS).
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-11-17 08:21:29 UTC
Issue summary: When an application passes a stack to
PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails,
OpenSSL frees every entry in the stack, both the old ones and any new
ones, but leaves them in the stack.

Impact summary: An application that passes an existing stack to
PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may
use memory that was already freed. This can cause a crash or, in
principle, memory corruption. Malformed PEM data can make the read fail,
but only applications that pass an existing stack are affected, and
OpenSSL itself does not do this.

CWE: CWE-416: Use After Free

Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and
private keys from PEM data and adds them to a stack of X509_INFO
structures. If the application passes a stack that is not NULL, the
function adds the new entries to it and must leave the entries that are
already there unchanged.

If reading fails, the function frees every entry in the stack. This
includes the entries that were there before the call, and the entries
added by the call. It does not remove these entries from the stack, so
the stack keeps pointers to freed memory. The failure can happen at any
point, even before any entry was added. A PEM item with invalid content
is enough.  This also happens if the stack was empty: entries added
before the failure are freed but stay in the stack.

An application that then reads or frees the stack will use memory that
was already freed. This can crash the application or, in principle,
corrupt memory.

Only applications that pass a stack that is not NULL are affected.
OpenSSL itself never does this. Its own callers, including the code that
TLS uses to load CA certificates, always pass NULL. When the stack is
NULL, the function frees only the entries that it created itself, which
is safe. We expect that very few applications pass an existing stack. An
attacker can make the read fail with malformed PEM data, but cannot make
an application pass an existing stack.

The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read()
and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and
1.0.2 have only the first two of these functions.

FIPS impact: no
The affected code is outside the FIPS module boundary.