# CVE-2026-45447: Heap Use-After-Free in the PKCS7_verify() Function > A crafted PKCS#7 message triggers a use-after-free in OpenSSL, potentially allowing remote code execution or crashes in applications processing signed messages. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 Jun 2026 - **Updated:** 18 Sep 2026 - **Also known as:** ALPINE-CVE-2026-45447, ALSA-2026:36215, ALSA-2026:44438, AZL-89811, AZL-89864, AZL-92837, BELL-CVE-2026-45447, CLSA-2026-1781175688, CLSA-2026-1781208261, CLSA-2026-1781209013, CLSA-2026-1781209312, CLSA-2026-1781253686, CLSA-2026-1781276539, CLSA-2026-1781343514, CLSA-2026-1781343538, CLSA-2026-1781549039, CLSA-2026-1782152516, CLSA-2026-1785154072, CLSA-2026-1785517004, CLSA-2026-1786005006, CLSA-2026-1786005845, CLSA-2026-1786006093, DEBIAN-CVE-2026-45447, GHSA-f684-cpcq-j565, JLSEC-2026-1145, MINI-cgvf-3w8p-hxpg, MINI-cj84-84rv-hf48, RHSA-2026:36215, RHSA-2026:44438, RLSA-2026:36215, RLSA-2026:44438, ROOT-OS-ALPINE-315-CVE-2026-45447, ROOT-OS-ALPINE-317-CVE-2026-45447, ROOT-OS-UBUNTU-2004-CVE-2026-45447, SUSE-SU-2026:2409-1, SUSE-SU-2026:2410-1, SUSE-SU-2026:2412-1, SUSE-SU-2026:2621-1, UBUNTU-CVE-2026-45447 ## What is CVE-2026-45447? CVE-2026-45447 is a high-severity use after free vulnerability in Openssl Openssl, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official 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. Weakness: CWE-825 (Expired Pointer Dereference), CWE-416 (Use After Free) ## Which versions are affected by CVE-2026-45447? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `compat-openssl10` | AlmaLinux:8 | All versions | 1:1.0.2o-4.el8_10.3 | | `compat-openssl11` | AlmaLinux:9 | All versions | 1:1.1.1k-5.el9_8.4 | | `compat-openssl10` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.0.2o-4.el8_10.3 | | `compat-openssl10-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.0.2o-4.el8_10.3 | | `compat-openssl10-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 1:1.0.2o-4.el8_10.3 | | `compat-openssl11` | Red Hat:enterprise_linux:9::appstream | All versions | 1:1.1.1k-5.el9_8.4 | | `compat-openssl10` | Rocky Linux:8 | All versions | 1:1.0.2o-4.el8_10.3 | | `compat-openssl11` | Rocky Linux:9 | All versions | 1:1.1.1k-5.el9_8.4 | | `openssl-1_1-livepatches` | SUSE:Linux Enterprise Live Patching 15 SP4 | All versions | 0.6-150400.3.20.1 | | `openssl-1_1-livepatches` | SUSE:Linux Enterprise Live Patching 15 SP5 | All versions | 0.6-150500.6.14.1 | | `openssl-1_1-livepatches` | SUSE:Linux Enterprise Live Patching 15 SP6 | All versions | 0.6-150600.11.6.1 | | `openssl-1_1-livepatches` | SUSE:Linux Enterprise Live Patching 15 SP7 | All versions | 0.6-150700.13.6.1 | Products: Openssl Openssl. ## How do I fix CVE-2026-45447? Apply the vendor's patch. ## Is CVE-2026-45447 being exploited? There is no known exploitation of CVE-2026-45447 in the wild and no public exploit code. Public exploit code: - CVE-2026-45447 (github_poc): https://github.com/0xredash/CVE-2026-45447 - CVE-2026-45447 - Draft (github_poc): https://github.com/HORKimhab/CVE-2026-45447 ## Other vulnerabilities in Openssl Openssl - [CVE-2009-3245](https://insights.sbomify.com/CVE-2009-3245/): Null dereference in n/a (critical 10.0) - [CVE-2006-3738](https://insights.sbomify.com/CVE-2006-3738/): Memory corruption in n/a (critical 10.0) - [CVE-2026-63073](https://insights.sbomify.com/CVE-2026-63073/): Untrusted Sender DN Used as Format String in CMP Response Validation (critical 9.8) - [CVE-2016-6309](https://insights.sbomify.com/CVE-2016-6309/): Use after free in n/a (critical 9.8) - [CVE-2016-0799](https://insights.sbomify.com/CVE-2016-0799/): Integer overflow in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-45447 and fix it if it is affected. What it is: CVE-2026-45447 is a high-severity use after free vulnerability in Openssl Openssl, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-45447 in the wild and no public exploit code. Affected product: Openssl Openssl. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-45447/ (Markdown: https://insights.sbomify.com/CVE-2026-45447/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45447 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45447 - OSV: https://osv.dev/vulnerability/CVE-2026-45447 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-45447/ Summaries are generated and may contain mistakes; the official description above is the record.