Skip to main content
VulnerabilityPublished

CVE-2026-107493: OpenSSL · Use After Free

Affects OpenSSLSource CVE Database V5

0
Compare

Not known to be exploited · fixed in 4.1.1 : patch OpenSSL soon.

Data as of 17 Nov 2026, 08:35 UTC

Severity
High

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

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
OpenSSLOpenSSLAffected
  • >=4.1.0 <4.1.1
Fixed in
  • 4.1.1
OpenSSLOpenSSLAffected
  • >=4.0.0 <4.0.4
Fixed in
  • 4.0.4
OpenSSLOpenSSLAffected
  • >=3.5.0 <3.5.10
Fixed in
  • 3.5.10
OpenSSLOpenSSLAffected
  • >=3.0.0 <3.0.24
Fixed in
  • 3.0.24
OpenSSLOpenSSLAffected
  • >=1.1.1 <1.1.1zk
Fixed in
  • 1.1.1zk
OpenSSLOpenSSLAffected
  • >=1.0.2 <1.0.2zt
Fixed in
  • 1.0.2zt

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

Community reviews

Loading reviews…