Skip to main content
CVE-2026-107493VulnerabilityPublished

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

0
Compare
Authoritative record:CVE-2026-107493· High

Not known to be exploited : upgrade to 3.0.0 soon.

Data as of 17 Nov 2026, 11:04 UTC

Severity
High

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

  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 org.openssl/openssl to 3.0.0.

Affected software

ProductAffectedFixed in
Mavenorg.openssl/opensslpkg:maven/org.openssl/opensslOther threatsAffected
  • <3.0.0
Fixed in
  • 3.0.0

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

Community reviews

Loading reviews…