Skip to content
OpenAdvisories
High · 7.7 CVE-2026-107493 EUVD-2026-126927GHSA-jvvm-vvmf-jf3r

Use-After-Free in PEM_X509_INFO_read_bio_ex() when appending to a caller-supplied stack fails

Published Nov 17, 2026 · Updated Nov 17, 2026 · Assigned by openssl

Description

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.

Affected products

VendorProductAffectedFixed
OpenSSL OpenSSL 4.1.0 – < 4.1.1, 4.0.0 – < 4.0.4, 3.5.0 – < 3.5.10, 3.0.0 – < 3.0.24, 1.1.1 – < 1.1.1zk, 1.0.2 – < 1.0.2zt 4.1.1

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Debian 14 openssl No fix yet —
Debian 13 openssl No fix yet —
Debian 12 openssl No fix yet —
ReleasePackageFixed inAdvisory
Ubuntu 26.10 edk2 +2 No fix yet —
Ubuntu 26.04 LTS edk2 +2 No fix yet —
Ubuntu 24.04 LTS edk2 +1 No fix yet —
Ubuntu 22.04 LTS edk2 +1 No fix yet —
Show 14 more (older releases, extended support, other products)
ReleasePackageFixed inAdvisory
Ubuntu Pro FIPS 20.04 LTS openssl No fix yet —
Ubuntu Pro FIPS 18.04 LTS openssl No fix yet —
Ubuntu Pro FIPS 16.04 LTS openssl No fix yet —
Ubuntu Pro FIPS-updates 24.04 LTS openssl-fips No fix yet —
Ubuntu Pro FIPS-updates 22.04 LTS openssl +1 No fix yet —
Ubuntu Pro FIPS-updates 20.04 LTS openssl No fix yet —
Ubuntu Pro FIPS-updates 18.04 LTS openssl No fix yet —
Ubuntu Pro FIPS-updates 16.04 LTS openssl No fix yet —
Ubuntu Pro FIPS-preview 22.04 LTS openssl +1 No fix yet —
Ubuntu Pro 22.04 LTS nodejs No fix yet —
Ubuntu Pro 20.04 LTS edk2 +1 No fix yet —
Ubuntu Pro 18.04 LTS edk2 +3 No fix yet —
Ubuntu Pro 16.04 LTS edk2 +2 No fix yet —
Ubuntu Pro 14.04 LTS openssl No fix yet —

Advisories 1

References