Loading vulnerability…
CVE-2026-58062 is a certificate-validation flaw in Bouncy Castle for Java in which a stapled OCSP response can be accepted without being properly bound to the certificate currently being validated. The issue affects Bouncy Castle for Java before 1.85, Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS before 2.0.2 in the 2.0.x series and 2.1.3 in the 2.1.x series. The vulnerable logic is identified in the provider OCSP revocation-checking path, including the ProvOcspRevocationChecker component. Because the stapled revocation response is not correctly tied to the checked certificate, certificate status validation can succeed based on an OCSP response that does not actually correspond to that certificate. This is an instance of improper certificate validation.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.