openssl · Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails
Affects opensslSource GCVE Database
Not known to be exploited : upgrade to 3.0.0 soon.
Data as of 17 Nov 2026, 11:04 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Affects
- OpenSSL prior to 3.0.0
- Patch
- Available – fixed in 3.0.0
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade org.openssl/openssl to 3.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavenorg.openssl/opensslpkg:maven/org.openssl/opensslOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to OpenSSL version 3.0.0 or later, where this issue is fixed. Applications should avoid passing existing stacks to PEM_X509_INFO_read_bio_ex() and related functions or ensure they do not use the stack after a failed read. Since OpenSSL itself does not pass existing stacks, the primary mitigation is to update affected applications or OpenSSL libraries to a fixed version.
Description
A use-after-free vulnerability exists in OpenSSL versions prior to 3.0.0 in the PEM_X509_INFO_read_bio_ex() function and related functions. When an application passes an existing stack to these functions and the read operation fails, OpenSSL frees all entries in the stack but leaves dangling pointers in the stack structure. This can lead to application crashes or memory corruption if the application continues to use the stack after failure. OpenSSL itself does not pass an existing stack, so this primarily affects third-party applications that do so. The issue is fixed in OpenSSL 3.0.0.
References
- nvd.nist.gov/vuln/detail/CVE-2026-107493 (opens in a new tab)
- github.com/openssl/openssl/commit/0486dfadfec558e1808f59d35a8d79e541c4e7d7 (opens in a new tab)
- github.com/openssl/openssl/commit/c57a5ccf0c060755b5494a6870922b7c6cdd7dd8 (opens in a new tab)
- github.com/openssl/openssl/commit/c8f6d04f8e6d40b1bf83334e4a2ec9daf5943a3d (opens in a new tab)
- openssl-library.org/news/secadv/20261117.txt (opens in a new tab)