Loading vulnerability…
CVE-2026-58061 affects Bouncy Castle Java CCM-family decryption implementations, including CCMBlockCipher, KCCMBlockCipher, and KGCMBlockCipher. These implementations write decrypted plaintext into caller-provided buffers before verifying the authentication tag. Applications that consume this output before detecting authentication failure may process tampered or unauthenticated data. Affected releases include Bouncy Castle for Java before 1.85, Java LTS before 2.73.12, and 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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An authenticated-encryption implementation flaw in Bouncy Castle Java CCM-family modes that writes plaintext into the caller-provided buffer before verifying the authentication tag. This can expose unauthenticated plaintext to application code.
A vulnerability in Bouncy Castle Java cryptographic libraries where CCM-family modes write plaintext to the caller buffer before authentication tag verification, potentially exposing unauthenticated plaintext and impacting integrity handling.
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.