Vulnerability · CVE-2026-22796
Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE union member is accessed without first validating the ty
Published Jan 27, 2026 · catalog updated Oct 15, 2026 · Issue summary: A type
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-22796. EPSS is 0.59%. Act only if a listed version of Issue summary: A type 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: A type).
- 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.3
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.59%
- Remediation
- Version ranges on file
- Affected products
- cpe openssl/openssl · vendor OpenSSL OpenSSL 3.3.0 <3.3.6
Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE 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 PKCS7_digest_from_attributes() function can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service. The function PKCS7_digest_from_attributes() accesses the message digest attribute value without validating its type. When the type is not V_ASN1_OCTET_STRING, this results in accessing invalid memory through the ASN1_TYPE 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.
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.0.2zn
- 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
- vendor OpenSSL OpenSSL 3.3.0 <3.3.63.3.0 <3.3.6
How to fix CVE-2026-22796
Upgrade
CVE-2026-22796 lists a fix boundary at 1.0.2zn. Compare the installed build with that boundary before you change production.
Version check
Affected < 1.0.2zn
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-22796. EPSS is 0.59%. Act only if a listed version of Issue summary: A type is installed.
Which versions are affected?
Compare what you have installed with OpenSSL OpenSSL 3.3.0 <3.3.6 3.3.0 <3.3.6. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-754. EPSS 0.59%. 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: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE 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 PKCS7_digest_from_attribut
Oct 15, 2026 · EUVD
Updated
Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE 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 PKCS7_digest_from_attribut
Sources
- CVE.orgVulnerability recordCVE-2026-22796
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-22796
30-day exploitation probability 0.59%
first.org - EUVDVulnerability recordEUVD-2026-4813
Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing malformed PKCS#7 data. Impact sum
euvd.enisa.europa.eu - Monitored products — criticalVendor advisoryCVE-2026-22796
Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE 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 PKCS7_digest_from_attribut
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