CVE-2026-45447

Heap Use-After-Free in the PKCS7_verify() Function

HIGH
8.8
CVSS Score
Published: June 9, 2026 at 04:03 PM UTC
Updated: September 18, 2026 at 01:18 PM UTC
3 products affected across 2 vendorsOpenSSLOpenShift Container PlatformHardened Images

Using OpenSSL by OpenSSL?

Get instant alerts when new vulnerabilities affect OpenSSL - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 4%
SSVC
No known exploit

Description

Issue summary: A specially crafted PKCS#7 or S/MIME signed message could trigger a use-after-free during PKCS#7 signature verification. Impact summary: A use-after-free may result in process crashes, heap corruption, or potentially remote code execution. When processing a PKCS#7 or S/MIME signed message, if the SignedData digestAlgorithms field is present as an empty ASN.1 SET, OpenSSL may incorrectly free a caller-owned BIO during PKCS7_verify(). A subsequent use of the BIO by the calling application results in a use-after-free condition. In the common case this occurs when the application later calls BIO_free() on the BIO originally passed to PKCS7_verify(). Depending on allocator behavior and application-specific BIO usage patterns, this may result in a crash or other memory corruption. In some application contexts this may potentially be exploitable for remote code execution. Applications that process PKCS#7 or S/MIME signed messages using OpenSSL PKCS#7 APIs may be affected. Applications using the CMS APIs for this processing are not affected. The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.0.2 ≤ v < 1.0.2zq1.1.1 ≤ v < 1.1.1zh3.0.0 ≤ v < 3.0.213.4.0 ≤ v < 3.4.63.5.0 ≤ v < 3.5.73.6.0 ≤ v < 3.6.34.0.0 ≤ v < 4.0.11.0.21.1.13.0.03.4.03.5.03.6.04.0.0
Affected range stops below 1.0.2zq, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.1.1zh, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.21, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.6.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.1, so it looks safe — our inference, not a vendor statement
All versions
Vendor states this is fixed in 412.86.202608241157-0 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHCISA-ADP
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416CWE-825

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card