CVE-2026-107493: Use-After-Free in PEM_X509_INFO_read_bio_ex() when appending to a caller-supplied stack fails
Issue summary: When an application passes a stack to PEMX509INFOreadbioex() 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 PEMX509INFOreadbioex() 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: PEMX509INFOreadbioex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509INFO 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 PEMX509INFOreadbio(), PEMX509INFOread() and PEMX509INFOreadex(), 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 Software
Event History
Frequently Asked Questions
Which applications are affected?
Only applications that call PEM_X509_INFO_read_bio_ex() with a non-NULL, pre-existing X509_INFO stack and then continue using that stack after the read fails are affected. OpenSSL itself does not use the function in this way.
What is required to trigger the issue?
The read operation must fail after the application supplies an existing stack. Malformed PEM data can cause such a failure.
What can happen after a failed read?
OpenSSL frees both the stack's pre-existing entries and entries added during the failed read, but leaves their pointers in the stack. Subsequent application use of that stack can cause a crash or, in principle, memory corruption.
How can developers determine whether their code is exposed?
Review calls to PEM_X509_INFO_read_bio_ex() for cases where the stack argument is non-NULL and retains entries from before the call. Those call paths are exposed if they can handle a failed read and later access or reuse the same stack.