CVE
OpenSSL use-after-free in PEM_X509_INFO_read_bio_ex()
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H · openssl rates this low
- Exploited
- No known exploitation
- Fix
- Fixed in 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, and 1 more
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, or one of 1 more.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.12% · 2nd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 28/100 · provisional
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- Low (openssl)
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In OpenSSL, a failed read in PEM_X509_INFO_read_bio_ex() frees the stack entries, including ones the application passed in, but leaves dangling pointers in the stack. Applications that pass an existing stack and keep using it after a failed read can crash or, in principle, corrupt memory, and malformed PEM data can trigger the failure.
Written by a model from the sources below. Verify against them.
Original 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.
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach20/20Affects OpenSSL (software on nearly every server, desktop or phone)
- Severity7.7/10CVSS 7.7
- No patch0/5No signal
What would change the score
- Would score about 83 if added to CISA KEV
- Would score about 78 if CISA's SSVC rates exploitation active
- Would score about 50 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, or one of 1 more.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-107493 (Use-After-Free in PEM_X509_INFO_read_bio_ex() when appending to a caller-supplied stack fails), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-107493 (entry last updated 2026-11-17):
Affected:
- OpenSSL OpenSSL: from 4.1.0, fixed in 4.1.1; from 4.0.0, fixed in 4.0.4; from 3.5.0, fixed in 3.5.10; from 3.0.0, fixed in 3.0.24; from 1.1.1, fixed in 1.1.1zk; from 1.0.2, fixed in 1.0.2zt
Fixed versions: 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, 1.0.2zt.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-107493 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-107493 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://openssl-library.org/news/secadv/20261117.txt
- https://github.com/openssl/openssl/commit/c57a5ccf0c060755b5494a6870922b7c6cdd7dd8
- https://github.com/openssl/openssl/commit/0486dfadfec558e1808f59d35a8d79e541c4e7d7
- https://github.com/openssl/openssl/commit/c8f6d04f8e6d40b1bf83334e4a2ec9daf5943a3d
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-107493
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-107493"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
- Posted on X by cve.now
Affected versions
- OpenSSL OpenSSL
From 4.1.0 · fixed in 4.1.1; From 4.0.0 · fixed in 4.0.4; From 3.5.0 · fixed in 3.5.10; From 3.0.0 · fixed in 3.0.24; From 1.1.1 · fixed in 1.1.1zk; From 1.0.2 · fixed in 1.0.2zt
Evidence 6
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-107493
Is CVE-2026-107493 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-107493?
OpenSSL: from 4.1.0 before 4.1.1; from 4.0.0 before 4.0.4; from 3.5.0 before 3.5.10; from 3.0.0 before 3.0.24; from 1.1.1 before 1.1.1zk; from 1.0.2 before 1.0.2zt.Source: cve.now feed data
How do I fix CVE-2026-107493?
Upgrade to a fixed version: 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, or one of 1 more.Source: cve.now feed data
Why is it rated 7.7 High?
CVSS 7.7 scores the worst case. openssl rates it Low.