CVE-2026-59650 is an improper input validation flaw in Bouncy Castle for Java before 1.85 and Bouncy Castle for Java LTS before 2.73.12. The issue affects the MTI/A0 Diffie-Hellman agreement implementation, identified in the DHAgreement component, where a peer-supplied Diffie-Hellman value is exponentiated without prior validation. In a key-agreement protocol, failure to validate the peer public value can allow malformed or adversarial inputs to be processed as if they were legitimate group elements, undermining the security assumptions of the exchange. The vulnerability affects all supported platforms using the vulnerable Java libraries.
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.