dbcve.org
CWE-354Weakness · CWE-354

CVE-2026-58061

HIGH · 8.7 CVSS v4.0 Published 2026-08-03
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 3 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Bouncy Castle for Java before 1.85, CCM-family modes write plaintext to caller buffer before tag check. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 (2.0.X series) and 2.1.3 (2.1.X series).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Bouncy Castle for Java, CCM-mode decryption writes plaintext to the caller's output buffer before verifying the authentication tag. This allows an attacker who can intercept and manipulate ciphertext to obtain decrypted plaintext even when the authentication tag is invalid, potentially enabling oracle attacks or information disclosure.

MitigationUpgrade Bouncy Castle Java to version 1.85+ (mainline), 2.73.12+ (LTS), or the appropriate FIPS version (bc-fips 1.0.2.7+, 2.0.2+, or 2.1.3+) to ensure the tag is verified before plaintext is returned.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Amber

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Bouncy Castle Java dependency
    Examine your project's build files (pom.xml, build.gradle), lib folder, or run 'jar tf bcprov*.jar | head' to confirm presence of org/bouncycastle/ packages. Also check classpath for bcprov, bcpkix, or bc-fips jars.
    Affected if Bouncy Castle Java library is not present in the environment
  2. Determine Bouncy Castle version
    For bcprov/bcpkix: check the jar filename (bcprov-jdk18on-1.84.jar), MANIFEST.MF inside the jar (Implementation-Version), or your dependency manager output. For bc-fips: check the jar name (bc-fips-1.0.2.6.jar) or MANIFEST.MF for Implementation-Version.
    Affected if Version is < 1.85, or < 2.73.12 for LTS branches, or < 1.0.2.7/2.0.2/2.1.3 for FIPS variants
  3. Identify CCM mode usage
    Search source code for 'CCM' mode in cipher initialization (Cipher.getInstance calls with 'CCM'), or review runtime configuration/logs if cryptographic operation logging is enabled. Look for patterns like 'AES/CCM' or 'AESCCM'.
    Affected if CCM mode is not used (other modes are not affected by this specific flaw)
  4. Check for oracle exposure
    Review whether the application exposes decryption success/failure to untrusted parties, exposes timing differences in authentication, or returns decrypted data before throwing security exceptions. Check error handling code paths for CCM decryption.
    Affected if Decryption output or timing is observable by attackers (required for exploitability)

You are affected if you use Bouncy Castle Java with a vulnerable version AND use CCM mode for decryption AND an attacker can observe decryption outcomes or timing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade Bouncy Castle Java to version 1.85+ (mainline), 2.73.12+ (LTS), or the appropriate FIPS version (bc-fips 1.0.2.7+, 2.0.2+, or 2.1.3+) to ensure the tag is verified before plaintext is returned.

Recommended fix Moderate confidence

Bouncy Castle Java 1.85 / 2.73.12 LTS / bc-fips 1.0.2.7 / 2.0.2 / 2.1.3 (depending on product line in use)

  1. Identify which Bouncy Castle for Java library version is in use (vanilla, LTS, or BC-FIPS)
  2. For vanilla Bouncy Castle Java: upgrade to version 1.85 or later
  3. For Bouncy Castle Java LTS: upgrade to version 2.73.12 or later
  4. For BC-FIPS 1.0.X series: upgrade to bc-fips 1.0.2.7 or later
  5. For BC-FIPS 2.0.X series: upgrade to bc-fips 2.0.2 or later
  6. For BC-FIPS 2.1.X series: upgrade to bc-fips 2.1.3 or later
  7. Verify the upgrade by running existing test suites and checking that CCM decryption operations now validate the authentication tag before returning plaintext

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58061 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-58061 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data