CVE-2026-45447 Affecting openssl-perl package, versions <1:3.5.5-4.el9_8


Severity

Recommended
high

Based on Rocky Linux security rating.

Threat Intelligence

EPSS
1.41% (70th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ROCKY9-OPENSSLPERL-17336160
  • published14 Jun 2026
  • disclosed9 Jun 2026

Introduced: 9 Jun 2026

NewCVE-2026-45447  (opens in a new tab)

How to fix?

Upgrade Rocky-Linux:9 openssl-perl to version 1:3.5.5-4.el9_8 or higher.
This issue was patched in RLSA-2026:25239.

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl-perl package and not the openssl-perl package as distributed by Rocky-Linux. See How to fix? for Rocky-Linux:9 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1