CVE-2026-107493 json
Use-After-Free in PEM_X509_INFO_read_bio_ex() when appending to a caller-supplied stack fails
published 2d ago modified yesterday also EUVD-2026-126927
- cvss
- 7.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- OpenSSL OpenSSL 1.0.2zt, 1.1.1zk, 3.0.24, 3.5.10, 4.0.4, 4.1.1
Is CVE-2026-107493 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-18).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.7 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
| CNA | 3.1 | 7.7 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
Affected products
- OpenSSL OpenSSL
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
-
github.com
/openssl/openssl/commit/c57a5ccf0c060755b5494a6870922b7c6cdd7dd8
patch
-
github.com
/openssl/openssl/commit/0486dfadfec558e1808f59d35a8d79e541c4e7d7
patch
-
github.com
/openssl/openssl/commit/c8f6d04f8e6d40b1bf83334e4a2ec9daf5943a3d
patch
-
openssl-library.org
/news/secadv/20261117.txt
vendor-advisory
Sources
- CVE List CVE-2026-107493
- NVD CVE-2026-107493
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.