Skip to main content
Mallory
High

NULL Dereference in OpenSSL Certificate Verification with OCSP Checking

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

CVE-2026-42765 is a NULL pointer dereference in OpenSSL certificate verification logic. The issue occurs when partial-chain verification is enabled together with OCSP response checking for the entire certificate chain. During OCSP response checking, the code assumes the next certificate in the verified chain is available as the issuer and attempts to access it. Although there is handling for self-signed certificates, when X509_V_FLAG_PARTIAL_CHAIN is enabled and the verified chain does not include a self-signed trusted anchor, the issuer for the last certificate in the chain is NULL. Dereferencing that NULL pointer causes the process to crash. The vulnerability affects OpenSSL 4.0.0 before 4.0.1 and 3.6.0 before 3.6.3. The affected code is outside the OpenSSL FIPS module boundary, and no FIPS modules are affected.

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 a process crash, resulting in denial of service. Based on the provided information, the impact is limited to application availability; no evidence is provided for code execution, memory corruption beyond the NULL dereference, confidentiality loss, or integrity compromise. Severity is described as Low because exploitation requires a non-default combination of certificate verification flags.

Mitigation

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

If immediate patching is not possible, avoid enabling the vulnerable flag combination together. Specifically, disable OCSP response checking for the whole chain (X509_V_FLAG_OCSP_RESP_CHECK_ALL) or disable partial-chain verification (X509_V_FLAG_PARTIAL_CHAIN). Because both options are disabled by default, applications that do not explicitly enable both settings are not affected.

Remediation

Patch, then assume compromise.

Upgrade to a fixed OpenSSL release: 4.0.1 or later for the 4.0 branch, or 3.6.3 or later for the 3.6 branch. More generally, apply the vendor-provided patch or consume the corrected package from your operating system or distribution channel if OpenSSL is supplied downstream.
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
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 activity

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