Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
Medium

NULL Pointer Dereference in OpenSSL Password-Based CMS Decryption

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

CVE-2026-42766 is a low-severity NULL pointer dereference in OpenSSL's password-based CMS decryption logic. A specially crafted password-encrypted CMS message can omit the optional PasswordRecipientInfo.keyDerivationAlgorithm field, which is permitted by the ASN.1 specification. During CMS decryption, the OpenSSL CMS implementation dereferences this field without first verifying that it is present. As a result, an application that processes attacker-supplied password-encrypted CMS content via the affected CMS decryption paths can crash. Reported affected versions are OpenSSL 4.0.0 before 4.0.1, 3.6.0 before 3.6.3, 3.5.0 before 3.5.7, 3.4.0 before 3.4.6, 3.0.0 before 3.0.21, 1.1.1 before 1.1.1zh, and 1.0.2 before 1.0.2zq. The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are stated to be unaffected because the vulnerable code lies outside the OpenSSL FIPS module boundary.

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 an application crash due to a NULL pointer dereference, resulting in denial of service. The available information does not indicate confidentiality, integrity, privilege-escalation, or code-execution impact for this CVE.

Mitigation

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

If immediate patching is not possible, avoid or restrict processing of untrusted password-encrypted CMS messages. Disable or limit password-based CMS decryption functionality where operationally feasible, and reduce exposure of applications that accept CMS input from untrusted or remote sources. No complete workaround is documented beyond applying the vendor fix.

Remediation

Patch, then assume compromise.

Upgrade OpenSSL to a fixed release: 4.0.1 or later, 3.6.3 or later, 3.5.7 or later, 3.4.6 or later, 3.0.21 or later, 1.1.1zh or later, or 1.0.2zq or later, as applicable to the deployed branch. Downstream consumers should also apply vendor-packaged updates such as the relevant Alpine, Debian, FreeBSD, Microsoft Mariner, or other distribution security updates that incorporate the OpenSSL fix.
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 activity10

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