# CVE-2026-8507: Crypt::OpenSSL::PKCS12 versions through 1.94 for Perl have out-of-bounds (OOB) write flaws

> A signed integer overflow in Crypt::OpenSSL::PKCS12 allows heap out-of-bounds writes and potential remote code execution when parsing large PKCS12 files.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 May 2026
- **Updated:** 18 May 2026
- **Also known as:** DEBIAN-CVE-2026-8507, GHSA-3qmj-qw66-fwx8, UBUNTU-CVE-2026-8507

## What is CVE-2026-8507?

CVE-2026-8507 is a critical vulnerability in JONASBN Crypt::OpenSSL::PKCS12, published on 17 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Crypt::OpenSSL::PKCS12 versions through 1.94 for Perl have out-of-bounds (OOB) write flaws.

When parsing a PKCS12 file, with a >= 1 GiB OCTET STRING (or BIT STRING) attribute on a SAFEBAG, via info() or info_as_hash(), a heap out-of-bounds write would be triggered with remote-code-execution potential (RCE) due to a signed integer overflow in the size calculation passed to Renew().

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-8507?


## How do I fix CVE-2026-8507?

Apply the vendor's patch.

## Is CVE-2026-8507 being exploited?

There is no known exploitation of CVE-2026-8507 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8507 and fix it if it is affected.

What it is: CVE-2026-8507 is a critical vulnerability in JONASBN Crypt::OpenSSL::PKCS12, published on 17 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8507 in the wild and no public exploit code.

Affected product: JONASBN Crypt::OpenSSL::PKCS12. 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-8507/ (Markdown: https://insights.sbomify.com/CVE-2026-8507/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8507
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8507
- OSV: https://osv.dev/vulnerability/CVE-2026-8507

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8507/
Summaries are generated and may contain mistakes; the official description above is the record.