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.
- BDU:2026-16119
- ALSA-2026:25237
- ALSA-2026:25239
- ALSA-2026:26275
- ALSA-2026:36215
- ALSA-2026:44438
- openSUSE-SU-2026:11023-1
- openSUSE-SU-2026:21005-1
- RHSA-2026:25237
- RHSA-2026:25239
- RHSA-2026:26275
- RHSA-2026:35869
- RHSA-2026:36215
- RHSA-2026:36217
- RHSA-2026:39009
- RHSA-2026:39012
- RHSA-2026:42825
- RHSA-2026:44438
- RHSA-2026:55543
- RHSA-2026:58563
- Published
- Jun 9, 2026
- Updated
- Sep 18, 2026
- EPSS
- 4.0% · 90th percentile
- CWE
- CWE-416
Report tools
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| openssl | openssl | cpe:2.3:a:openssl:openssl |
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 checkAffected 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.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | openssl | before 1:3.5.5-4.el10_2.alma.1 | 1:3.5.5-4.el10_2.alma.1 |
| AlmaLinux:10 | openssl-devel | before 1:3.5.5-4.el10_2.alma.1 | 1:3.5.5-4.el10_2.alma.1 |
| AlmaLinux:10 | openssl-libs | before 1:3.5.5-4.el10_2.alma.1 | 1:3.5.5-4.el10_2.alma.1 |
| AlmaLinux:10 | openssl-perl | before 1:3.5.5-4.el10_2.alma.1 | 1:3.5.5-4.el10_2.alma.1 |
| AlmaLinux:8 | compat-openssl10 | before 1:1.0.2o-4.el8_10.3 | 1:1.0.2o-4.el8_10.3 |
| AlmaLinux:8 | openssl | before 1:1.1.1k-16.el8_6 | 1:1.1.1k-16.el8_6 |
| AlmaLinux:8 | openssl-devel | before 1:1.1.1k-16.el8_6 | 1:1.1.1k-16.el8_6 |
| AlmaLinux:8 | openssl-libs | before 1:1.1.1k-16.el8_6 | 1:1.1.1k-16.el8_6 |
| AlmaLinux:8 | openssl-perl | before 1:1.1.1k-16.el8_6 | 1:1.1.1k-16.el8_6 |
| AlmaLinux:9 | compat-openssl11 | before 1:1.1.1k-5.el9_8.4 | 1:1.1.1k-5.el9_8.4 |
| AlmaLinux:9 | openssl | before 1:3.5.5-4.el9_8 | 1:3.5.5-4.el9_8 |
| AlmaLinux:9 | openssl-devel | before 1:3.5.5-4.el9_8 | 1:3.5.5-4.el9_8 |
| AlmaLinux:9 | openssl-libs | before 1:3.5.5-4.el9_8 | 1:3.5.5-4.el9_8 |
| AlmaLinux:9 | openssl-perl | before 1:3.5.5-4.el9_8 | 1:3.5.5-4.el9_8 |
| Alpine:v3.21 | openssl | from 1.0.2 · before 3.3.7-r1 | 3.3.7-r1 |
| Alpine:v3.22 | openssl | from 1.0.2 · before 3.5.7-r0 | 3.5.7-r0 |
| Debian:12 | openssl | before 3.0.20-1~deb12u2 | 3.0.20-1~deb12u2 |
| Debian:13 | openssl | before 3.5.6-1~deb13u2 | 3.5.6-1~deb13u2 |
| Debian:14 | openssl | before 3.6.3-1 | 3.6.3-1 |
| openSUSE:Leap 16.0 | openssl-3 | before 3.5.0-160000.8.1 | 3.5.0-160000.8.1 |
| openSUSE:Tumbleweed | openssl-3 | before 3.5.3-6.1 | 3.5.3-6.1 |
| Red Hat:enterprise_linux_eus:10.0 | openssl | before 1:3.2.2-16.el10_0.7 | 1:3.2.2-16.el10_0.7 |
| Red Hat:enterprise_linux_eus:10.0 | openssl-debuginfo | before 1:3.2.2-16.el10_0.7 | 1:3.2.2-16.el10_0.7 |
| Red Hat:enterprise_linux_eus:10.0 | openssl-debugsource | before 1:3.2.2-16.el10_0.7 | 1:3.2.2-16.el10_0.7 |
+96
Same product
openssl: all recordsOther 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 remKEV90Now
- CVE-2021-3711SM2 Decryption Buffer Overflow65This 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() Path30Monitor
- ← EarlierCVE-2026-45446Jun 9, 2026 · Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes19Monitor
- Later →CVE-2026-7383Jun 9, 2026 · Possible Heap Buffer Overflow in ASN.1 Multibyte String Conversion32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| OpenSSL OpenSSL | 3.0.21 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.4.6 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.5.7 | Vendor (CNA) |
| OpenSSL OpenSSL | 3.6.3 | Vendor (CNA) |
| OpenSSL OpenSSL | 4.0.1 | Vendor (CNA) |
| azl3 edk2 20240524git3e722403cd16-17 on Azure Linux 3.0 | 20240524git3e722403cd16-18 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 openssl 3.3.7-3 on Azure Linux 3.0 | 3.3.7-4 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:compat-openssl10 | 1:1.0.2o-4.el8_10.3 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:compat-openssl11 | 1:1.1.1k-5.el9_8.4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:openssl | 1:3.5.5-4.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:openssl-devel | 1:3.5.5-4.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:openssl-libs | 1:3.5.5-4.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:openssl-perl | 1:3.5.5-4.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| alpine:openssl | 3.3.7-r1 · Alpine:v3.21 | Package registry (OSV) |
| debian:openssl | 3.0.20-1~deb12u2 · Debian:12 | Package registry (OSV) |
| opensuse:openssl-3 | 3.5.3-6.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:compat-openssl10 | 1:1.0.2o-4.el8_10.3 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:compat-openssl10-debuginfo | 1:1.0.2o-4.el8_10.3 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:compat-openssl11 | 1:1.1.1k-5.el9_6.3 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:compat-openssl11-debuginfo | 1:1.1.1k-5.el9_6.3 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:compat-openssl11-debugsource | 1:1.1.1k-5.el9_6.3 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:openssl | 1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:openssl-debuginfo | 1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:openssl-debugsource | 1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:openssl-devel | 1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:openssl-libs | 1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:openssl-libs-debuginfo | 1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:openssl-perl | 1:3.5.5-4.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| rocky linux:compat-openssl10 | 1:1.0.2o-4.el8_10.3 · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:compat-openssl11 | 1:1.1.1k-5.el9_8.4 · Rocky Linux:9 | Package 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.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2026-06-11 |
| Proof-of-concept repository on GitHub | stars:1 | 2026-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.
- Published
- First PoC+1 d
- TodayOct 22, 2026+135 d
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.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Igor Ustinovremediation developer
- Thai Duong (Calif.io in collaborationClaude and Anthropic Research)reporter
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 Code32Monitor
- CVE-2026-84783112 days apartUse-After-Free in X.509 Extension Cache Under Concurrent Use30Monitor
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.
- TR-26-0355 · Jun 10, 2026(OpenSSL Güvenlik Zafiyeti)
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 FreeCVSS 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.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);Fixed
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- github.com/openssl/openssl/commit/7d4a980c62258c5910cc883936e0c8dbab4d75a8
- github.com/openssl/openssl/commit/9dfd688ad2290fc5075cacbc9bf0c9a93eefed54
- github.com/openssl/openssl/commit/a541ae8bfe849a30cc885e8780715c0f488e496c
- github.com/openssl/openssl/commit/c505d7559da5d5f9f2c3913c6883a5562ce7273e
- openssl-library.org/news/secadv/20260609.txt
- access.redhat.com/errata/RHSA-2026:25237
- access.redhat.com/errata/RHSA-2026:25239
- access.redhat.com/errata/RHSA-2026:26275
- access.redhat.com/errata/RHSA-2026:26319
- access.redhat.com/errata/RHSA-2026:29197
- access.redhat.com/errata/RHSA-2026:34102
- access.redhat.com/errata/RHSA-2026:35869
- access.redhat.com/errata/RHSA-2026:36215
- access.redhat.com/errata/RHSA-2026:36217
- access.redhat.com/errata/RHSA-2026:39009
- access.redhat.com/errata/RHSA-2026:39012
- access.redhat.com/errata/RHSA-2026:39981
- access.redhat.com/errata/RHSA-2026:44438
- access.redhat.com/errata/RHSA-2026:47735
Vendor advisories and official records. Exploit/PoC links are deliberately left out.