CVE-2026-22796: ASN1_TYPE Type Confusion in the PKCS7_digest_from_attributes() function

Published Jan 16, 2026
·
Updated

Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing malformed PKCS#7 data.

Impact summary: An application performing signature verification of PKCS#7 data or calling directly the PKCS7digestfromattributes() function can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.

The function PKCS7digestfromattributes() accesses the message digest attribute value without validating its type. When the type is not VASN1OCTETSTRING, this results in accessing invalid memory through the ASN1TYPE union, causing a crash.

Exploiting this vulnerability requires an attacker to provide a malformed signed PKCS#7 to an application that verifies it. The impact of the exploit is just a Denial of Service, the PKCS7 API is legacy and applications should be using the CMS API instead. 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 PKCS#7 parsing implementation is outside the OpenSSL FIPS module boundary.

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

Affected Software

13 affected components
OpenSSL OpenSSL>=1.0.2<3.6
OpenSSL OpenSSL
OpenSSL OpenSSL>=1.0.2<1.0.2zn
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 to a version that resolves this vulnerability.

    Fixed in 1.0.2zn
  2. Upgrade

    Upgrade OpenSSL to a version that resolves this vulnerability.

    Fixed in 1.1.1ze
  3. Upgrade

    Upgrade OpenSSL to a version that resolves this vulnerability.

    Fixed in 3.0.19
  4. Upgrade

    Upgrade OpenSSL to a version that resolves this vulnerability.

    Fixed in 3.3.6
  5. Upgrade

    Upgrade OpenSSL to a version that resolves this vulnerability.

    Fixed in 3.4.4
  6. Upgrade

    Upgrade OpenSSL to a version that resolves this vulnerability.

    Fixed in 3.5.5
  7. Upgrade

    Upgrade OpenSSL to a version that resolves this vulnerability.

    Fixed in 3.6.1
  8. Compensating control

    If feasible, avoid using the legacy PKCS#7 API for signature verification; instead use the CMS API (the material notes applications should be using the CMS API instead).

Event History

Jan 16, 2026
Data Sourced
via Red Hat·02:45 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-22796?

CVE-2026-22796 is classified as a high severity vulnerability due to the potential for type confusion resulting in application crashes or arbitrary code execution.

2

How do I fix CVE-2026-22796?

You can fix CVE-2026-22796 by updating OpenSSL to a version that includes the patches addressing the ASN1_TYPE type confusion.

3

Which versions of OpenSSL are affected by CVE-2026-22796?

CVE-2026-22796 affects OpenSSL versions from 1.0.2 to 3.6, inclusive.

4

What is the impact of CVE-2026-22796 on applications?

The impact of CVE-2026-22796 can lead to crashes or unexpected behavior in applications that rely on PKCS#7 signature verification.

5

What is the nature of the vulnerability in CVE-2026-22796?

CVE-2026-22796 is a type confusion vulnerability that occurs when an ASN1_TYPE union member is accessed without proper type validation.

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