Loading vulnerability…
CVE-2026-59646 is a CWE-789 excessive-size memory-allocation vulnerability in the Bouncy Castle TLS DTLS handshake reassembler. When processing DTLS handshake fragments, the reassembler uses an unchecked attacker-controlled 24-bit length to allocate a buffer. Affected releases are Bouncy Castle for Java before 1.85, Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle FIPS TLS releases before 1.0.24, 2.0.24, and 2.1.24 in their respective release branches.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An unchecked 24-bit length used by the DTLS handshake reassembler to allocate a buffer in Bouncy Castle Java implementations. Affected versions include Bouncy Castle for Java before 1.85, Java LTS before 2.73.12, and specified BC-FJA bctls-fips releases before 1.0.24, 2.0.24, and 2.1.24.
A high-severity memory allocation / memory corruption vulnerability in the DTLS handshake reassembler of Bouncy Castle Java libraries caused by allocating a buffer from an unchecked 24-bit length.
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.