Loading vulnerability…
CVE-2026-58059 is an inefficient algorithmic complexity vulnerability in Bouncy Castle's X.500 distinguished-name stringification. Escaping during string conversion takes quadratic time, allowing crafted distinguished names to trigger excessive CPU consumption and potentially denial of service. Affected releases are Bouncy Castle for Java before 1.85, Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before 1.0.2.7 in the 1.0.X series, 2.0.2 in the 2.0.X series, and 2.1.3 in the 2.1.X series.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A quadratic-time escaping flaw when Bouncy Castle Java components stringify X.500 distinguished names, potentially enabling denial of service through disproportionate processing of crafted input.
A high-severity inefficient algorithmic complexity vulnerability in Bouncy Castle Java libraries that can lead to denial of service via quadratic-time escaping when stringifying X.500 distinguished names.
One of a cluster of Bouncy Castle vulnerabilities in a sustained campaign affecting security boundaries across Java, LTS, and FIPS lines; exact flaw details are not provided in the content.
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.