Bug 2430389 (CVE-2026-22795) - CVE-2026-22795 openssl: OpenSSL: Denial of Service due to type confusion in PKCS#12 file processing
Summary: CVE-2026-22795 openssl: OpenSSL: Denial of Service due to type confusion in P...
Keywords:
Status: NEW
Alias: CVE-2026-22795
Deadline: 2026-01-27
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-01-16 14:43 UTC by OSIDB Bzimport
Modified: 2026-02-23 22:59 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2026:1601 0 None None None 2026-01-29 20:11:06 UTC
Red Hat Product Errata RHBA-2026:1605 0 None None None 2026-01-29 22:38:42 UTC
Red Hat Product Errata RHBA-2026:1875 0 None None None 2026-02-04 04:58:33 UTC
Red Hat Product Errata RHSA-2026:1472 0 None None None 2026-01-28 08:56:48 UTC
Red Hat Product Errata RHSA-2026:1473 0 None None None 2026-01-28 09:54:18 UTC

Description OSIDB Bzimport 2026-01-16 14:43:55 UTC
Severity: Low

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.

OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.

OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.

OpenSSL 3.4 users should upgrade to OpenSSL 3.4.4.

OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.

OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.

OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1ze.
(premium support customers only).

Comment 2 errata-xmlrpc 2026-01-28 08:56:46 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:1472 https://access.redhat.com/errata/RHSA-2026:1472

Comment 3 errata-xmlrpc 2026-01-28 09:54:16 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:1473 https://access.redhat.com/errata/RHSA-2026:1473


Note You need to log in before you can comment on or make changes to this bug.