OpenSSLFramework / library
CVE-2026-22796
A fix is available.
Upgrade to 1.0.2zn / 1.1.1ze or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable
No privileges
Zero-click
Patch available
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIssue 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisA detailed technical summary for this CVE is being prepared.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
OpenSSLFramework / library
Affected:
>= 1.0.2, < 1.0.2zn>= 1.1.1, < 1.1.1ze>= 3.0.0, < 3.0.19>= 3.3.0, < 3.3.6>= 3.4.0, < 3.4.4>= 3.5.0, < 3.5.5>= 3.6.0, < 3.6.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped
Upgrade available
Upgrade to 1.0.2zn / 1.1.1ze / 3.0.19 or later
Fixed in
1.0.2zn1.1.1ze3.0.19
Vendor patch
github.com →
Recommended fix
High confidence
OpenSSL 1.0.2zn, 1.1.1ze, 3.0.19, or 3.3.6 (depending on branch)
- Identify the currently installed OpenSSL version using 'openssl version -a'
- Determine which version branch is in use (1.0.2, 1.1.1, 3.0.x, or 3.3.x)
- Obtain the fixed OpenSSL release for your branch: 1.0.2zn for 1.0.2 branch, 1.1.1ze for 1.1.1 branch, 3.0.19 for 3.0.x branch, or 3.3.6 for 3.3.x branch
- Download the appropriate source tarball from https://www.openssl.org/source/ or use your system's package manager
- Compile and install the new version, or apply the system package update
- Restart any services that use OpenSSL to ensure the patched version is loaded
- Verify the fix by checking 'openssl version' shows the patched release
Caveat OpenSSL 1.0.2 and 1.1.1 are end-of-life; consider migrating to 3.x branches for long-term support
Generated from the published advisory — verify against the referenced sources before acting.
We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600.
Get the upgrade done
Scan for this in your stack
Free · runs locally
dbcve dependency scanner
Check whether your project pulls in CVE-2026-22796 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22796 in production — separate from our analysis above.
Know something about CVE-2026-22796?
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
What this is
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
What belongs here
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data