CVE-2026-107493: OpenSSL · Use After Free
Affects OpenSSLSource CVE Database V5
Not known to be exploited · fixed in 4.1.1 : patch OpenSSL soon.
Data as of 17 Nov 2026, 08:35 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 4.1.1, 4.0.4, 3.5.10 +3
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 to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenSSLOpenSSL | Affected
| Fixed in
|
| OpenSSLOpenSSL | Affected
| Fixed in
|
| OpenSSLOpenSSL | Affected
| Fixed in
|
| OpenSSLOpenSSL | Affected
| Fixed in
|
| OpenSSLOpenSSL | Affected
| Fixed in
|
| OpenSSLOpenSSL | Affected
| Fixed in
|
AI-suggested
Fixed versions of OpenSSL are available: 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, and 1.0.2zt. Users and developers should upgrade to these versions to remediate the vulnerability. Since OpenSSL itself does not pass existing stacks, applications should avoid passing non-NULL stacks to these functions or ensure proper handling after a failed read. Patch status is confirmed by the presence of fixed versions.
Description
CVE-2026-107493 is a use-after-free vulnerability in OpenSSL's PEM_X509_INFO_read_bio_ex() 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 cause the application to access freed memory, potentially leading to crashes or memory corruption. OpenSSL itself does not pass existing stacks, so this issue primarily affects third-party applications that misuse the API. The vulnerability affects multiple OpenSSL versions prior to their respective fixed releases.
References
- openssl-library.org/news/secadv/20261117.txt (opens in a new tab)
- github.com/openssl/openssl/commit/c57a5ccf0c060755b5494a6870922b7c6cdd7dd8 (opens in a new tab)
- github.com/openssl/openssl/commit/0486dfadfec558e1808f59d35a8d79e541c4e7d7 (opens in a new tab)
- github.com/openssl/openssl/commit/c8f6d04f8e6d40b1bf83334e4a2ec9daf5943a3d (opens in a new tab)