Skip to main content
Mallory
Medium

NULL Pointer Dereference in OpenSSL Password-Based CMS Decryption

IdentifiersCVE-2026-42766CWE-476· NULL Pointer Dereference

CVE-2026-42766 is a NULL pointer dereference vulnerability in OpenSSL's handling of password-based CMS decryption. A specially crafted password-encrypted CMS message can omit the optional ASN.1 field PasswordRecipientInfo.keyDerivationAlgorithm. During CMS decryption, the OpenSSL CMS implementation dereferences this field without first verifying that it is present, causing a NULL pointer dereference. The issue affects applications that process attacker-supplied password-encrypted CMS messages using OpenSSL CMS decryption functionality.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation causes the target application to crash during password-based CMS decryption, resulting in denial of service. Based on the provided information, the impact is limited to process termination/application crash; no evidence is provided for code execution, privilege escalation, or confidentiality/integrity compromise. The OpenSSL FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected because the vulnerable code is outside the FIPS module boundary.

Mitigation

If you can’t patch tonight, do this now.

Avoid processing untrusted password-encrypted CMS messages until patched OpenSSL versions are deployed. Where feasible, disable or restrict password-based CMS decryption functionality, limit exposure of interfaces that accept CMS input from untrusted sources, and isolate or harden applications that must process such content to reduce denial-of-service impact.

Remediation

Patch, then assume compromise.

Upgrade OpenSSL to a fixed release. The provided content states fixes are available in OpenSSL 4.0.1, 3.6.3, 3.5.7, 3.4.6, 3.0.21, 1.1.1zh, and 1.0.2zq. Downstream vendors may ship backported fixes in their own package versions, so vendor-supported patched packages should also be considered acceptable remediation.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

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
FreebsdFreebsdapplication
OpenSSL Software FoundationOpensslapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

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, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.