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

Published May 27, 2026
·
Updated

Heap Use-After-Free in OpenSSL PKCS7verify()

Heap Use-After-Free in OpenSSL PKCS7verify() (CVE-2026-45447) Severity: High

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 PKCS7verify(). 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 BIOfree() on the BIO originally passed to PKCS7verify(). 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.

OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1, and 1.0.2 are vulnerable to this issue.

OpenSSL 4.0 users should upgrade to OpenSSL 4.0.1 OpenSSL 3.6 users should upgrade to OpenSSL 3.6.3. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.7. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.6. OpenSSL 3.0 users should upgrade to OpenSSL 3.0.21. OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zh (premium support customers only). OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zq (premium support customers only).

This issue was reported by Thai Duong (Calif.io in collaboration with Claude and Anthropic Research). on 27th April 2026. The fix was developed by Igor Ustinov.

Other sources

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

Microsoft

Affected Software

11 affected componentsFixes available
OpenSSL OpenSSL
debian/openssl<=1.1.1w-0+deb11u1, <=1.1.1w-0+deb11u7, <=3.0.20-1~deb12u1, <=3.5.6-1~deb13u1, <=3.6.2-1
3.0.20-1~deb12u23.5.6-1~deb13u2
Microsoft azl3 edk2 20240524git3e722403cd16-17<20240524git3e722403cd16-18
20240524git3e722403cd16-18
OpenSSL OpenSSL>=1.0.2<1.0.2zq
OpenSSL OpenSSL>=1.1.1<1.1.1zh
OpenSSL OpenSSL>=3.0.0<3.0.21
OpenSSL OpenSSL>=3.4.0<3.4.6
OpenSSL OpenSSL>=3.5.0<3.5.7
OpenSSL OpenSSL>=3.6.0<3.6.3
OpenSSL OpenSSL=4.0.0
Microsoft azl3 openssl 3.3.7-3<3.3.7-4
3.3.7-4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/openssl to a version that resolves this vulnerability.

    Fixed in 3.0.20-1~deb12u2Fixed in 3.5.6-1~deb13u2
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 20240524git3e722403cd16-18
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.3.7-4
  4. Upgrade

    Upgrade OpenSSL 1.0.2 to a version that resolves this vulnerability.

    Fixed in 1.0.2zq
  5. Upgrade

    Upgrade OpenSSL 1.1.1 to a version that resolves this vulnerability.

    Fixed in 1.1.1zh
  6. Upgrade

    Upgrade OpenSSL 3.0 to a version that resolves this vulnerability.

    Fixed in 3.0.21
  7. Upgrade

    Upgrade OpenSSL 3.4 to a version that resolves this vulnerability.

    Fixed in 3.4.6
  8. Upgrade

    Upgrade OpenSSL 3.5 to a version that resolves this vulnerability.

    Fixed in 3.5.7
  9. Upgrade

    Upgrade OpenSSL 3.6 to a version that resolves this vulnerability.

    Fixed in 3.6.3
  10. Upgrade

    Upgrade OpenSSL 4.0 to a version that resolves this vulnerability.

    Fixed in 4.0.1

Event History

May 27, 2026
Data Sourced
via Red Hat·02:23 PM
DescriptionSeverityAffected Software
Jun 9, 2026
CVE Published
via MITRE·04:03 PM
Data Sourced
via MITRE·04:03 PM
DescriptionWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
RemedyAffected Software
Data Sourced
via Ubuntu·08:07 PM
RemedyDescriptionSeverityAffected Software
Jun 10, 2026
Data Sourced
via Debian·08:09 PM
DescriptionAffected Software
Data Sourced
via Launchpad·08:09 PM
Description
Jun 13, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:02 AM
DescriptionSeverity
Updated
via Microsoft·08:02 AM
Affected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-45447?

CVE-2026-45447 has a critical severity rating of 9.8 according to the CVSS v3.1 scoring.

2

What is the main issue with CVE-2026-45447?

CVE-2026-45447 involves a heap use-after-free vulnerability in the PKCS7_verify() function during the processing of specially crafted PKCS#7 or S/MIME signed messages.

3

How do I fix CVE-2026-45447?

To remediate CVE-2026-45447, update to the latest version of OpenSSL that includes the security patch addressing this vulnerability.

4

Which software is affected by CVE-2026-45447?

CVE-2026-45447 affects OpenSSL and its implementations in Debian/openssl.

5

What types of attacks can exploit CVE-2026-45447?

CVE-2026-45447 can potentially be exploited by attackers delivering specially crafted signed messages to trigger the use-after-free vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203