Skip to content
Noroxi
CVE-2026-45447· NVD / CVE Program· CNA openssl

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

Noroxi assessment

Priority: Monitor (action score 36/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 4% (FIRST EPSS); higher than 90.4% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: OpenSSL OpenSSL 3.0.21, 3.4.6, 3.5.7; azl3 edk2 20240524git3e722403cd16-17 on Azure Linux 3.0 20240524git3e722403cd16-18; azl3 openssl 3.3.7-3 on Azure Linux 3.0 3.3.7-4.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to OpenSSL OpenSSL 3.0.21, 3.4.6, 3.5.7; azl3 edk2 20240524git3e722403cd16-17 on Azure Linux 3.0 20240524git3e722403cd16-18; azl3 openssl 3.3.7-3 on Azure Linux 3.0 3.3.7-4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 8.8 · v3.1—Proof of concept Fix available
Published
Jun 9, 2026
Updated
Sep 18, 2026
EPSS
4.0% · 90th percentile

Report tools

JSON

Action score

36

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 4.0%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-45447

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
opensslopenssl

Check your server's TLS configuration

The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.

Run the SSL check

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • openssl openssl1.0.2 and later · before 1.0.2zq
  • openssl openssl1.1.1 and later · before 1.1.1zh
  • openssl openssl3.0.0 and later · before 3.0.21
  • openssl openssl3.4.0 and later · before 3.4.6
  • openssl openssl3.5.0 and later · before 3.5.7
  • openssl openssl3.6.0 and later · before 3.6.3
  • openssl openssl4.0.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.

  • OpenSSL OpenSSL

    • 4.0.0 and later · before 4.0.1affected · semver
    • 3.6.0 and later · before 3.6.3affected · semver
    • 3.5.0 and later · before 3.5.7affected · semver
    • 3.4.0 and later · before 3.4.6affected · semver
    • 3.0.0 and later · before 3.0.21affected · semver
    • 1.1.1 and later · before 1.1.1zhaffected
    • 1.0.2 and later · before 1.0.2zqaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10opensslbefore 1:3.5.5-4.el10_2.alma.11:3.5.5-4.el10_2.alma.1
AlmaLinux:10openssl-develbefore 1:3.5.5-4.el10_2.alma.11:3.5.5-4.el10_2.alma.1
AlmaLinux:10openssl-libsbefore 1:3.5.5-4.el10_2.alma.11:3.5.5-4.el10_2.alma.1
AlmaLinux:10openssl-perlbefore 1:3.5.5-4.el10_2.alma.11:3.5.5-4.el10_2.alma.1
AlmaLinux:8compat-openssl10before 1:1.0.2o-4.el8_10.31:1.0.2o-4.el8_10.3
AlmaLinux:8opensslbefore 1:1.1.1k-16.el8_61:1.1.1k-16.el8_6
AlmaLinux:8openssl-develbefore 1:1.1.1k-16.el8_61:1.1.1k-16.el8_6
AlmaLinux:8openssl-libsbefore 1:1.1.1k-16.el8_61:1.1.1k-16.el8_6
AlmaLinux:8openssl-perlbefore 1:1.1.1k-16.el8_61:1.1.1k-16.el8_6
AlmaLinux:9compat-openssl11before 1:1.1.1k-5.el9_8.41:1.1.1k-5.el9_8.4
AlmaLinux:9opensslbefore 1:3.5.5-4.el9_81:3.5.5-4.el9_8
AlmaLinux:9openssl-develbefore 1:3.5.5-4.el9_81:3.5.5-4.el9_8
AlmaLinux:9openssl-libsbefore 1:3.5.5-4.el9_81:3.5.5-4.el9_8
AlmaLinux:9openssl-perlbefore 1:3.5.5-4.el9_81:3.5.5-4.el9_8
Alpine:v3.21opensslfrom 1.0.2 · before 3.3.7-r13.3.7-r1
Alpine:v3.22opensslfrom 1.0.2 · before 3.5.7-r03.5.7-r0
Debian:12opensslbefore 3.0.20-1~deb12u23.0.20-1~deb12u2
Debian:13opensslbefore 3.5.6-1~deb13u23.5.6-1~deb13u2
Debian:14opensslbefore 3.6.3-13.6.3-1
openSUSE:Leap 16.0openssl-3before 3.5.0-160000.8.13.5.0-160000.8.1
openSUSE:Tumbleweedopenssl-3before 3.5.3-6.13.5.3-6.1
Red Hat:enterprise_linux_eus:10.0opensslbefore 1:3.2.2-16.el10_0.71:3.2.2-16.el10_0.7
Red Hat:enterprise_linux_eus:10.0openssl-debuginfobefore 1:3.2.2-16.el10_0.71:3.2.2-16.el10_0.7
Red Hat:enterprise_linux_eus:10.0openssl-debugsourcebefore 1:3.2.2-16.el10_0.71:3.2.2-16.el10_0.7

+96

Other highest-scoring records for the same primary product.

  • CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remKEV
    90Now
  • CVE-2021-3711SM2 Decryption Buffer Overflow
    65This week
  • CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code
    65This week

Published before and after this one in the same product

  • ← EarlierCVE-2026-45445Jun 9, 2026 · AES-OCB IV Ignored on EVP_Cipher() Path
    30Monitor
  • ← EarlierCVE-2026-45446Jun 9, 2026 · Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes
    19Monitor
  • Later →CVE-2026-7383Jun 9, 2026 · Possible Heap Buffer Overflow in ASN.1 Multibyte String Conversion
    32Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
OpenSSL OpenSSL3.0.21Vendor (CNA)
OpenSSL OpenSSL3.4.6Vendor (CNA)
OpenSSL OpenSSL3.5.7Vendor (CNA)
OpenSSL OpenSSL3.6.3Vendor (CNA)
OpenSSL OpenSSL4.0.1Vendor (CNA)
azl3 edk2 20240524git3e722403cd16-17 on Azure Linux 3.020240524git3e722403cd16-18 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 openssl 3.3.7-3 on Azure Linux 3.03.3.7-4 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:compat-openssl101:1.0.2o-4.el8_10.3 · AlmaLinux:8Package registry (OSV)
almalinux:compat-openssl111:1.1.1k-5.el9_8.4 · AlmaLinux:9Package registry (OSV)
almalinux:openssl1:3.5.5-4.el10_2.alma.1 · AlmaLinux:10Package registry (OSV)
almalinux:openssl-devel1:3.5.5-4.el10_2.alma.1 · AlmaLinux:10Package registry (OSV)
almalinux:openssl-libs1:3.5.5-4.el10_2.alma.1 · AlmaLinux:10Package registry (OSV)
almalinux:openssl-perl1:3.5.5-4.el10_2.alma.1 · AlmaLinux:10Package registry (OSV)
alpine:openssl3.3.7-r1 · Alpine:v3.21Package registry (OSV)
debian:openssl3.0.20-1~deb12u2 · Debian:12Package registry (OSV)
opensuse:openssl-33.5.3-6.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:compat-openssl101:1.0.2o-4.el8_10.3 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:compat-openssl10-debuginfo1:1.0.2o-4.el8_10.3 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:compat-openssl111:1.1.1k-5.el9_6.3 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:compat-openssl11-debuginfo1:1.1.1k-5.el9_6.3 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:compat-openssl11-debugsource1:1.1.1k-5.el9_6.3 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:openssl1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:openssl-debuginfo1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:openssl-debugsource1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:openssl-devel1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:openssl-libs1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:openssl-libs-debuginfo1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:openssl-perl1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
rocky linux:compat-openssl101:1.0.2o-4.el8_10.3 · Rocky Linux:8Package registry (OSV)
rocky linux:compat-openssl111:1.1.1k-5.el9_8.4 · Rocky Linux:9Package registry (OSV)

+6

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02026-06-11
Proof-of-concept repository on GitHubstars:12026-06-13

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+1 d
  3. TodayOct 22, 2026+135 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-2838763 days apartPotential Use-after-free in DANE Client Code
    32Monitor
  • CVE-2026-84783112 days apartUse-After-Free in X.509 Extension Cache Under Concurrent Use
    30Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records