CVE-2026-22796: ASN1_TYPE Type Confusion in the PKCS7_digest_from_attributes() function
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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-22796 is an OpenSSL PKCS#7 parsing flaw that can crash applications verifying specially malformed signed PKCS#7 data. Sources describe denial of service only, not data theft or code execution. Business urgency is highest for services that accept untrusted signed PKCS#7 inputs.
Executive priority
Treat as a targeted availability risk, not a breach-class issue. Prioritize patching internet-facing or high-availability services that process signed PKCS#7 from users, partners, email, update packages, or document workflows.
Technical view
PKCS7_digest_from_attributes() reads a message digest attribute through an ASN1_TYPE union without confirming it is V_ASN1_OCTET_STRING. A malformed type can trigger invalid or NULL pointer dereference during PKCS#7 signature verification. OpenSSL says the legacy PKCS#7 API is affected; FIPS modules are not.
Likely exposure
Exposure is likely limited to applications using OpenSSL PKCS#7 signature verification, or directly calling PKCS7_digest_from_attributes(), on affected OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1, or 1.0.2 versions.
Exploitation context
The source bundle does not show active exploitation, and KEV is false. Exploitation requires delivering malformed signed PKCS#7 data to an application that verifies it. The stated impact is denial of service through process crash.
Researcher notes
The bug is CWE-754 improper exceptional-condition handling. The key validation point is whether malformed PKCS#7 reaches OpenSSL signature verification. Sources identify patches for OpenSSL 3.6.1, 3.5.5, 3.4.4, 3.3.6, and 3.0.19 commits; legacy branch handling needs vendor confirmation.
Mitigation direction
Upgrade affected OpenSSL 3.x branches to vendor-fixed releases where available.
For OpenSSL 1.1.1 or 1.0.2, check vendor or support-channel guidance.
Prefer the CMS API over legacy PKCS#7 APIs where feasible.
Reduce exposure to untrusted PKCS#7 inputs until patched.
Confirm downstream vendors have shipped patched OpenSSL builds.
Validation and detection
Inventory OpenSSL versions in applications, containers, appliances, and packaged dependencies.
Identify code paths that verify signed PKCS#7 data.
Check for direct calls to PKCS7_digest_from_attributes().
Verify OpenSSL is patched to the relevant fixed branch release.
Confirm FIPS module use does not hide affected non-FIPS PKCS#7 parsing.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-754: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-754 · source CWE mapping
Improper Check for Unusual or Exceptional Conditions
Improper Check for Unusual or Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.