Bouncy Castle is a widely used Java crypto library; this flaw causes unauthenticated plaintext leakage in AEAD (CCM) and can affect many Java apps and services.
CVE-2026-58061
Bouncy Castle CCM modes may write plaintext before tag verification.
Is CVE-2026-58061 being exploited?
Not confirmed. CVE-2026-58061 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.
How severe is CVE-2026-58061?
CVE-2026-58061 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-58061?
Yes. A fix has been recorded for CVE-2026-58061. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-58061 affect?
CVE-2026-58061 affects Bouncy Castle for Java < 1.85, Bouncy Castle Java LTS < 2.73.12, Bouncy Castle FIPS (bc-fips) 1.0.X < 1.0.2.7, 2.0.X < 2.0.2, 2.1.X < 2.1.3. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-58061?
Upgrade BC Java to >=1.85, LTS to >=2.73.12, and bc-fips to the fixed releases immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated plaintext disclosure: manipulated ciphertext can cause decrypted data to be written to caller buffers before tag check, risking data leakage if apps use the buffer.
Immediate action required
- affected>= 1.0.0 and < 1.0.2.7
- affected>= 2.0.0 and < 2.0.2
- affected>= 2.1.0 and < 2.1.3
- affected< 1.85
- affected>= 2.73.0 and < 2.73.12
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.