# CVE-2026-9265: Crypt::OpenSSL::PKCS12 versions before 1.96 for Perl permits a heap OOB read in print_attribute UTF8STRING path

> An attacker can trigger a heap out-of-bounds read in the Perl Crypt::OpenSSL::PKCS12 library, potentially disclosing sensitive memory contents.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 20 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-9265, GHSA-597h-8vxx-6jqw, UBUNTU-CVE-2026-9265

## What is CVE-2026-9265?

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

### Official description

Crypt::OpenSSL::PKCS12 versions before 1.96 for Perl permits a heap OOB read in print_attribute UTF8STRING path.

print_attribute() copies a UTF8STRING ASN.1 attribute value into a heap buffer sized exactly to its declared length via strncpy, leaving no NUL terminator. Downstream callers run strlen() on the result and pass the inflated length to newSVpvn(), copying attacker-influenced adjacent heap bytes into a Perl scalar.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Upgrade to a fixed version.

## Is CVE-2026-9265 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9265 is a critical memory corruption vulnerability in JONASBN Crypt::OpenSSL::PKCS12, published on 20 Jun 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-9265 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-9265/ (Markdown: https://insights.sbomify.com/CVE-2026-9265/index.md)
```

## Sources

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

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