OpenSSL · OpenSSL · published 2026-11-17
CVE-2026-107493Use-After-Free in PEM_X509_INFO_read_bio_ex() when appending to a caller-supplied stack fails
Routine No exploitation evidence; EPSS 0.1%.
CVE-2026-107493 is not known to be exploited in the wild. EPSS estimates a 0.1% chance of exploitation in the next 30 days, higher than 3% of all CVEs. This OpenSSL vulnerability: CVSS 7.7 (v3.1). Fixed upstream in OpenSSL 4.1.1, 4.0.4, 3.5.10, 3.0.24 (+2 more); Debian and Ubuntu still have unfixed releases. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in OpenSSL 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, 1.0.2zt.
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | openssl | No fix yet |
| 12 bookworm | openssl | No fix yet | |
| Ubuntu (+4 more packages) | 26.04 LTS | openssl | No fix yet |
| 24.04 LTS | openssl | No fix yet | |
| 22.04 LTS | openssl | No fix yet |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
Crypto libraryOpenSSL
OpenSSL security fixes: 3 CVEs
Upgrade to
4.1.14.0.43.5.103.0.241.1.1zk1.0.2ztWhy: Vendor security release for server software (most severe: CVE-2026-107493).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.1% (4th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.7 (v3.1)CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- OpenSSL OpenSSL
4.1.0to before4.1.1(affected)4.0.0to before4.0.4(affected)3.5.0to before3.5.10(affected)3.0.0to before3.0.24(affected)1.1.1to before1.1.1zk(affected)1.0.2to before1.0.2zt(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.