CVE-2026-22796Medium· 5.3▾ SunlitIssue 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 p…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 29.2 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the CISA ADP record, not NVD.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.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.
OpenSSL >= 3.6.0 < 3.6.1OpenSSL >= 3.5.0 < 3.5.5OpenSSL >= 3.4.0 < 3.4.4OpenSSL >= 3.3.0 < 3.3.6OpenSSL >= 3.0.0 < 3.0.19OpenSSL >= 1.1.1 < 1.1.1zeOpenSSL >= 1.0.2 < 1.0.2znRefer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-22795Medium· 5.5Missing ASN1_TYPE validation in PKCS#12 parsing
CVE-2025-69420High· 7.5Missing ASN1_TYPE validation in TS_RESP_verify_response() function
CVE-2025-68160Medium· 4.7Heap out-of-bounds write in BIO_f_linebuffer on short writes
CVE-2025-69419High· 7.4Out of bounds write in PKCS12_get_friendlyname() UTF-8 conversion
CVE-2025-69421High· 7.5NULL Pointer Dereference in PKCS12_item_decrypt_d2i_ex function
CVE-2025-69418Medium· 4.0Unauthenticated/unencrypted trailing bytes with low-level OCB function calls