Loading vulnerability…
CVE-2026-35188 is a double-free vulnerability in OpenSSL's TLS client certificate verification path when processing an OCSP stapled response delivered through the TLS status_request extension. A malicious server can send a crafted stapled OCSP response that triggers a double-free when the client checks the stapled response during certificate status evaluation. The flaw affects client-side processing and is only reachable when OCSP stapling support is enabled on the TLS client. The vulnerable code is outside the OpenSSL FIPS module boundary, so FIPS modules are not affected.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An OpenSSL double-free vulnerability during OCSP stapling/certificate status evaluation that can be triggered by a malicious external server, leading primarily to application crash.
A moderate OpenSSL double-free vulnerability in TLS client OCSP stapling response handling that may cause denial of service and potentially code execution in complex environments.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.