CVE-2026-22796: Type Confusion in OpenSSL PKCS#7 Signature Verification
- Vendor
- OpenSSL Software Foundation
CVE-2026-22796 is a type confusion vulnerability in OpenSSL's legacy PKCS#7 signature verification implementation. PKCS7_digest_from_attributes() accesses the message-digest attribute through an ASN1_TYPE union without checking that its type is V_ASN1_OCTET_STRING. A malformed signed PKCS#7 object containing an unexpected attribute type can therefore trigger an invalid or NULL pointer dereference during a read, crashing the application. Vulnerable releases occur in the OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1, and 1.0.2 branches. The OpenSSL FIPS modules in branches 3.5, 3.4, 3.3, and 3.0 are unaffected because PKCS#7 parsing is outside their module boundaries.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation causes an application crash and denial of service when the application verifies malformed signed PKCS#7 data or directly calls PKCS7_digest_from_attributes() with malformed attributes. The established impact is limited to availability; code execution, information disclosure, and integrity compromise are not established. OpenSSL assessed the issue as Low severity because of its limited impact and reliance on the legacy PKCS#7 API.
Mitigation
If you can’t patch tonight, do this now.
Avoid the vulnerable legacy PKCS#7 verification path and use the CMS API instead where feasible. Until patched, prevent untrusted PKCS#7 objects from reaching affected verification routines by restricting input sources or disabling the relevant processing feature. Isolate verification workloads to limit the operational impact of crashes.
Remediation
Patch, then assume compromise.
Upgrade OpenSSL to 3.6.1, 3.5.5, 3.4.4, 3.3.6, or 3.0.19, or a later fixed release in the corresponding branch. For vendor-packaged or embedded OpenSSL, install the vendor's security update containing the fix. Fixed release numbers for the affected 1.1.1 and 1.0.2 branches are not specified. Restart applications using the updated library to ensure the patched code is loaded.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-22796 exploited in the wild?
- As of Nov 7, 2026, Mallory has no reports of CVE-2026-22796 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-22796?
- As of Nov 7, 2026, Mallory has found no public exploit for CVE-2026-22796.
- Is there a patch for CVE-2026-22796?
- Upgrade OpenSSL to 3.6.1, 3.5.5, 3.4.4, 3.3.6, or 3.0.19, or a later fixed release in the corresponding branch. For vendor-packaged or embedded OpenSSL, install the vendor's security update containing the fix.
- What products are affected by CVE-2026-22796?
- OpenSSL Software Foundation Openssl.
- How severe is CVE-2026-22796?
- CVE-2026-22796 has a CVSS v3.1 score of 5.3 (Medium) and an EPSS score of 0.59% (49th percentile) as of Nov 7, 2026.
Recent activity
54 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.