Read the docs

Use-after-free in OpenSSL PEM_X509_INFO_read_bio_ex() on failed read

Priority LOW 38CWE-416Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
—
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from CNA.

Summary

Versions from 4.1.0 before 4.1.1, 4.0.0 before 4.0.4, 3.5.0 before 3.5.10, 3.0.0 before 3.0.24, 1.1.1 before 1.1.1zk and 1.0.2 before 1.0.2zt of OpenSSL are affected. When PEM_X509_INFO_read_bio_ex() fails while appending to a caller-supplied stack, it frees the existing and new entries but leaves them in the stack, a use after free (CWE-416). An application that keeps using that stack may crash or corrupt memory, and malformed PEM data can trigger the failure.

Written with Claude Haiku 5.5 from the sources below · 2026-11-17

Description from the CNA

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.

Why it matters now

Fix Fixed OpenSSL (OpenSSL): 4.1.1, 4.0.4, 3.5.10 +3

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
OpenSSLOpenSSL4.1.0 to before 4.1.1; 4.0.0 to before 4.0.4; 3.5.0 to before 3.5.10; 3.0.0 to before 3.0.24; 1.1.1 to before 1.1.1zk; 1.0.2 to before 1.0.2zt4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, 1.0.2ztPatch availableCNA
  • OpenSSL VendorOpenSSL Affected 4.1.0 to before 4.1.1; 4.0.0 to before 4.0.4; 3.5.0 to before 3.5.10; 3.0.0 to before 3.0.24; 1.1.1 to before 1.1.1zk; 1.0.2 to before 1.0.2zt Fixed in 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, 1.0.2zt Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*——OpenSSL
  • cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* Versions — — ·OpenSSL

Remediation

Upgrade OpenSSL to 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk or 1.0.2zt, depending on the release branch in use.

Written with Claude Haiku 5.5 from the sources below · 2026-11-17

  • Fix · CNA OpenSSL (OpenSSL) Fixed in 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, 1.0.2zt

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Advisory ·

    OpenSSL — openssl-library.org/news/secadv/20261117.txt

    3 records Highest priority Priority LOW 3 LOW

    Other records, highest priority first

    • TI-2026-92465 Unbounded memory retention in OpenSSL QUIC server for rejected streamsPriority LOW 38
    • TI-2026-92463 Out-of-bounds read in OpenSSL TLS key-share processing with Suite BPriority LOW 38

Timeline

  1. 2026-11-17 Threatist record created from CVE-2026-107493
  2. 2026-11-17 Alias added: GHSA-jvvm-vvmf-jf3r

References

  • TI-2022-01915 The c_rehash script allows command injection CVSS 3.1CRITICAL 9.8
  • TI-2021-02645 SM2 Decryption Buffer Overflow CVSS 3.1CRITICAL 9.8
  • TI-2009-03392 The TLS protocol, and the SSL protocol 3.0 and possibly earlier, as used in Microsoft… CVSS 3.1CRITICAL 9.8
  • TI-2022-01176 The c_rehash script allows command injection CVSS 3.1CRITICAL 9.8
  • TI-2014-00154 Out-of-bounds read in OpenSSL TLS and DTLS Heartbeat handling KEVCVSS 3.1HIGH 7.5
  • TI-2025-14107 Stack buffer overflow in CMS (Auth)EnvelopedData parsing CVSS 3.1HIGH 8.8
See all 328 →

Sources