Vulnerability · CVE-2026-22795
Issue summary: An invalid or NULL pointer dereference can happen in an application processing a malformed PKCS#12 file.
Published Jan 27, 2026 · catalog updated Oct 15, 2026 · Issue summary: An invalid
Last checked Nov 5, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-22795. EPSS is 0.18%. Act only if a listed version of Issue summary: An invalid is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Issue summary: An invalid).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-84783 · High
- CVE-2026-84782 · High
- CVE-2026-77696 · Low
- CVE-2026-75806 · Medium
- CVE-2026-75805 · Medium
- Severity
- Medium5.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.18%
- Remediation
- Version ranges on file
- Affected products
- cpe openssl/openssl · vendor OpenSSL OpenSSL 3.5.0 <3.5.5
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe openssl/openssl< 1.1.1ze
- cpe openssl/openssl< 3.0.19
- cpe openssl/openssl< 3.3.6
- cpe openssl/openssl< 3.4.4
- cpe openssl/openssl< 3.5.5
- cpe openssl/openssl< 3.6.1
- vendor OpenSSL OpenSSL 3.5.0 <3.5.53.5.0 <3.5.5
How to fix CVE-2026-22795
Upgrade
CVE-2026-22795 lists a fix boundary at 1.1.1ze. Compare the installed build with that boundary before you change production.
Version check
Affected < 1.1.1ze
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-22795. EPSS is 0.18%. Act only if a listed version of Issue summary: An invalid is installed.
Which versions are affected?
Compare what you have installed with OpenSSL OpenSSL 3.5.0 <3.5.5 3.5.0 <3.5.5. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-754. EPSS 0.18%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Jan 27, 2026 · EUVD
Detected
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 w
Oct 15, 2026 · EUVD
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 ASN1_TYPE union member is accessed w
Sources
- CVE.orgVulnerability recordCVE-2026-22795
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-22795
30-day exploitation probability 0.18%
first.org - EUVDVulnerability recordEUVD-2026-4815
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
euvd.enisa.europa.eu - Monitored products — criticalVendor advisoryCVE-2026-22795
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 w
nvd.nist.gov
References
Freshness
Last verified in this catalog Nov 5, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 5, 2026
- Monitored products — criticalNov 4, 2026
- CVE.orgNov 4, 2026
- EUVDNov 2, 2026