Skip to main content
Mallory
HighVulnerability

CVE-2026-45447: Heap Use-After-Free in OpenSSL PKCS7_verify()

Published Jun 9, 2026 · Updated 5 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days17 mentions · peak 4 in a dayToday
CVSS8.1High · v3.1
EPSS4.0%91st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
OpenSSL Software Foundation
IdentifiersCVE-2026-45447CWE-416 · Use After Free

CVE-2026-45447 is a heap use-after-free vulnerability in OpenSSL PKCS#7 signature verification. When processing a specially crafted PKCS#7 or S/MIME signed message whose SignedData digestAlgorithms field is present as an empty ASN.1 SET, PKCS7_verify() may incorrectly free a caller-owned BIO. Subsequent application use of that BIO, commonly a BIO_free() call on the originally supplied object, accesses freed memory. Consequences include process crashes, heap corruption, and potentially remote code execution, depending on allocator behavior and application-specific BIO usage. Applications using CMS APIs for this processing are unaffected. OpenSSL FIPS modules in versions 4.0, 3.6, 3.5, 3.4, and 3.0 are unaffected because the vulnerable code is outside the FIPS module boundary; this does not establish that applications using those modules are unaffected.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can crash the application performing signature verification, causing denial of service, or corrupt its heap through subsequent use or freeing of the prematurely released BIO. In some application contexts, the memory corruption may permit remote code execution and compromise the confidentiality and integrity of data accessible to the affected process. Code execution is a potential outcome, not an assured consequence of triggering the flaw.

Mitigation

If you can’t patch tonight, do this now.

Until patched, disable or avoid processing untrusted PKCS#7 or S/MIME signed messages through OpenSSL PKCS#7 APIs where feasible. Use the unaffected CMS APIs for this processing path when application compatibility permits. Restrict access to services accepting externally supplied signed messages and isolate message-processing components to reduce exposure and potential impact. These measures do not replace updating the vulnerable library.

Remediation

Patch, then assume compromise.

Install the vendor-fixed OpenSSL packages or update the product that bundles the affected library. Confirmed fixed packages include Debian bookworm openssl 3.0.20-1~deb12u2 and trixie openssl 3.5.6-1~deb13u2; RHEL 9.4 compat-openssl11 1.1.1k-5.el9_4.3 under RHSA-2026:39009; and RHEL 9.2 compat-openssl11 1.1.1k-4.el9_2.2 under RHSA-2026:39012. Alpine Linux fixes are included in releases 3.22.5, 3.23.5, and 3.24.1. Use the applicable vendor advisory to select the correct fixed package for other products and support streams. Restart affected applications after updating so that they load the corrected libraries.

Public exploits

Exploits

No validated public exploits yet. Hidden: 2 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
OpenSSL Software FoundationOpensslapplication
FAQ

Frequently asked questions

Is CVE-2026-45447 exploited in the wild?
As of Nov 12, 2026, Mallory has no reports of CVE-2026-45447 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-45447?
As of Nov 12, 2026, Mallory has found no public exploit for CVE-2026-45447.
Is there a patch for CVE-2026-45447?
Install the vendor-fixed OpenSSL packages or update the product that bundles the affected library. Confirmed fixed packages include Debian bookworm openssl 3.0.20-1~deb12u2 and trixie openssl 3.5.6-1~deb13u2; RHEL 9.4 compat-openssl11 1.1.1k-5.el9_4.3 under RHSA-2026:39009; and RHEL 9.2 compat-openssl11 1.1.1k-4.el9_2.2 under RHSA-2026:39012.
What products are affected by CVE-2026-45447?
OpenSSL Software Foundation Openssl.
How severe is CVE-2026-45447?
CVE-2026-45447 has a CVSS v3.1 score of 8.1 (High) and an EPSS score of 4.0% (91st percentile) as of Nov 12, 2026.
Activity feed

Recent activity

160 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 11, 2026Rocky Linux 9.6 [CIQ] Security Update: compat-openssl11 Multip... | Tenable®A vulnerability affecting compat-openssl11 on Rocky Linux 9.6. A security update is available under CIQ advisory ciqsa-2026_1774; technical details and individual exploitation status are not provided.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.1 : openssl (EulerOS-SA-2026-4773) | Tenable®An empty SignedData digestAlgorithms set can cause PKCS7_verify() to incorrectly free a caller-owned BIO. Subsequent application use or freeing of that BIO can cause crashes, heap corruption, or potentially remote code execution, depending on allocator behavior and application usage. Applications using OpenSSL PKCS#7 APIs may be affected; those using CMS APIs for this processing are unaffected.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.1 : shim (EulerOS-SA-2026-4795) | Tenable®When a PKCS#7 SignedData digestAlgorithms field contains an empty ASN.1 SET, OpenSSL's PKCS7_verify() may incorrectly free a caller-owned BIO. Subsequent application use or freeing of that BIO can cause crashes, heap corruption, or potentially remote code execution. Applications processing PKCS#7 or S/MIME messages through OpenSSL's PKCS#7 APIs may be affected; CMS APIs and the listed FIPS modules are unaffected. Updated shim packages are available for affected EulerOS Virtualization installations.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.0 : shim (EulerOS-SA-2026-4854) | Tenable®OpenSSL's PKCS7_verify() may incorrectly free a caller-owned BIO when a signed message contains an empty SignedData digestAlgorithms SET. Subsequent application use or freeing of that BIO can cause a use-after-free, crashes, heap corruption, or potentially remote code execution. Applications processing PKCS#7 or S/MIME messages through OpenSSL's PKCS#7 APIs may be affected; CMS APIs and the listed FIPS modules are unaffected. The advisory identifies affected EulerOS Virtualization shim packages; Nessus relies on reported versions rather than testing exploitation.Read more ↗
+76 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity40Community discussion across Reddit, Mastodon, and other social sources.