# CVE-2026-22795: Missing ASN1_TYPE validation in PKCS#12 parsing

> An attacker can cause a denial of service by tricking an application into processing a malformed PKCS#12 file, triggering a null pointer dereference in OpenSSL.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Jan 2026
- **Updated:** 15 Oct 2026
- **Also known as:** ALPINE-CVE-2026-22795, AZL-75275, AZL-75789, AZL-75893, AZL-76119, AZL-76155, AZL-78552, BELL-CVE-2026-22795, CLEANSTART-2026-JU79609, DEBIAN-CVE-2026-22795, ECHO-7300-0df7-ef21, GHSA-3vqq-45qg-2xf6, JLSEC-2026-269, MINI-646c-qwjc-fhrr, MINI-h6gv-9hjf-vpch, MINI-jm44-f3x4-62cq, UBUNTU-CVE-2026-22795

## What is CVE-2026-22795?

CVE-2026-22795 is a medium-severity vulnerability in Openssl Openssl, published on 27 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Issue summary: An invalid or NULL pointer dereference can happen in
an application processing a malformed PKCS#12 file.

Impact summary: An application processing a malformed PKCS#12 file can be
caused to dereference an invalid or NULL pointer on memory read, resulting
in a Denial of Service.

A type confusion vulnerability exists in PKCS#12 parsing code where
an ASN1_TYPE union member is accessed without first validating the type,
causing an invalid pointer read.

The location is constrained to a 1-byte address space, meaning any
attempted pointer manipulation can only target addresses between 0x00 and 0xFF.
This range corresponds to the zero page, which is unmapped on most modern
operating systems and will reliably result in a crash, leading only to a
Denial of Service. Exploiting this issue also requires a user or application
to process a maliciously crafted PKCS#12 file. It is uncommon to accept
untrusted PKCS#12 files in applications as they are usually used to store
private keys which are trusted by definition. For these reasons, the issue
was assessed as Low severity.

The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,
as the PKCS12 implementation is outside the OpenSSL FIPS module boundary.

OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.

OpenSSL 1.0.2 is not affected by this issue.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

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

It affects 1 product.


Products: Openssl Openssl.

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

Apply the vendor's patch.

## Is CVE-2026-22795 being exploited?

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

## 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-22795 and fix it if it is affected.

What it is: CVE-2026-22795 is a medium-severity vulnerability in Openssl Openssl, published on 27 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-22795 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-22795/ (Markdown: https://insights.sbomify.com/CVE-2026-22795/index.md)
```

## Sources

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

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