Skip to main content
Mallory
MediumVulnerability

CVE-2026-22796: Type Confusion in OpenSSL PKCS#7 Signature Verification

Published Jan 27, 2026 · Updated 9 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 2 in a dayToday
CVSS5.3Medium · v3.1
EPSS0.59%49th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
OpenSSL Software Foundation
IdentifiersCVE-2026-22796CWE-843

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
OpenSSL Software FoundationOpensslapplication
FAQ

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.
Activity feed

Recent activity

54 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+18 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity22Community discussion across Reddit, Mastodon, and other social sources.