Loading vulnerability…
CVE-2026-58060 is an excessive-memory-allocation vulnerability in Bouncy Castle's Hierarchical Signature System (HSS) verification handling. An unbounded HSS public-key level count allows attacker-controlled verification input to trigger huge memory allocations, potentially causing denial of service. Affected versions include Bouncy Castle for Java before 1.85, Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before 2.0.2 in the 2.0.x series and before 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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An unbounded HSS public-key level-count flaw in Bouncy Castle for Java that can cause huge memory allocation during signature verification, potentially resulting in denial of service.
A high-severity denial-of-service vulnerability in Bouncy Castle Java libraries caused by an unbounded HSS public-key level count, which can trigger excessive memory allocation during signature verification.
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.