CVE-2026-107493

7.7High

Published 17 Nov 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.1-flash-lite

7.7CVSS

High

0CVSS v3.110

Attack vector
Local
Complexity
Low
Privileges
None
User action
None
Impact
High impact on confidentiality, availability
Weakness
CWE-416

What an attacker gets

Attackers can trigger a use-after-free crash or memory corruption by providing malformed PEM data to applications. This only affects applications that pass an existing, non-NULL stack to specific OpenSSL PEM reading functions.

Root cause

The PEM_X509_INFO_read functions incorrectly free all entries in a provided stack upon failure, leaving dangling pointers to freed memory.

Affected versions

OpenSSL 1.0.2, 1.1.1, and subsequent versions using the affected PEM_X509_INFO_read functions.

CVSS v3.1 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Fix & remediation

Upgrade to the latest OpenSSL release provided by your distribution. If you maintain custom code, ensure you pass NULL as the stack argument to PEM_X509_INFO_read_bio_ex and related functions.

remediation — bash
$ sudo apt-get update && sudo apt-get install --only-upgrade openssl

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD 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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-107493