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

Published Jan 16, 2026
·
Updated

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 ASN1TYPE 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.

Affected Software

11 affected components
OpenSSL OpenSSL>=1.1.1<3.7.0
OpenSSL OpenSSL>=1.1.1<1.1.1ze
OpenSSL OpenSSL>=3.0.0<3.0.19
OpenSSL OpenSSL>=3.3.0<3.3.6
OpenSSL OpenSSL>=3.4.0<3.4.4
OpenSSL OpenSSL>=3.5.0<3.5.5
OpenSSL OpenSSL>=3.6.0<3.6.1
IBM Verify Identity Access<=11.0 - 11.0.2
IBM Security Verify Access<=10.0 - 10.0.9.1
IBM Verify Identity Access Container<=11.0 - 11.0.2
IBM Security Verify Access Container<=10.0 - 10.0.9.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade OpenSSL 1.1.1 to a version that resolves this vulnerability.

    Fixed in 1.1.1ze
  2. Upgrade

    Upgrade OpenSSL 3.0 to a version that resolves this vulnerability.

    Fixed in 3.0.19
  3. Upgrade

    Upgrade OpenSSL 3.3 to a version that resolves this vulnerability.

    Fixed in 3.3.6
  4. Upgrade

    Upgrade OpenSSL 3.4 to a version that resolves this vulnerability.

    Fixed in 3.4.4
  5. Upgrade

    Upgrade OpenSSL 3.5 to a version that resolves this vulnerability.

    Fixed in 3.5.5
  6. Upgrade

    Upgrade OpenSSL 3.6 to a version that resolves this vulnerability.

    Fixed in 3.6.1
  7. Compensating control

    Avoid processing maliciously crafted/untrusted PKCS#12 files in applications; only process PKCS#12 files that are trusted by definition (e.g., private keys which are trusted by definition).

Event History

Jan 16, 2026
Data Sourced
via Red Hat·02:43 PM
DescriptionSeverityAffected Software
Jan 27, 2026
CVE Published
via MITRE·04:01 PM
Data Sourced
via MITRE·04:01 PM
DescriptionWeakness
Data Sourced
via NVD·04:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 8, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-22795?

CVE-2026-22795 is a high-severity vulnerability due to potential application crashes from NULL pointer dereference.

2

How does CVE-2026-22795 affect OpenSSL applications?

CVE-2026-22795 affects OpenSSL applications processing malformed PKCS#12 files, leading to application instability.

3

How do I fix CVE-2026-22795?

To fix CVE-2026-22795, users should update OpenSSL to a version later than 3.7.0 or implement workarounds for file validation.

4

What versions of OpenSSL are affected by CVE-2026-22795?

CVE-2026-22795 affects OpenSSL versions from 1.1.1 up to 3.7.0.

5

Can CVE-2026-22795 lead to data loss?

CVE-2026-22795 can potentially lead to data loss if applications crash unexpectedly while processing malformed files.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203