CVE-2025-8885: Bouncy Castle for Java on All (API modules) allows Excessive Allocation

CVE-2025-8885 · Severity: medium · CVSS 4 · Published 2025-08-12

Bouncy Castle for Java on All (API modules) allows Excessive Allocation

Technologies: org.bouncycastle:bc-fips (Maven), org.bouncycastle:bcprov-jdk14 (Maven), org.bouncycastle:bcprov-jdk15to18 (Maven), org.bouncycastle:bcprov-jdk18on (Maven), org.bouncycastle:bctls-jdk14 (Maven), org.bouncycastle:bctls-jdk15to18 (Maven), org.bouncycastle:bctls-jdk18on (Maven). Vendors: Maven.

Quick answers

Is CVE-2025-8885 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-8885 being exploited in the wild.
How severe is CVE-2025-8885?
Medium severity, with a CVSS score of 4, published 12 August 2025.
Which products and versions are affected?
org.bouncycastle:bc-fips (Maven) ECOSYSTEM:introduced=1.0.0,fixed=1.0.2.6; org.bouncycastle:bcprov-jdk14 (Maven) ECOSYSTEM:introduced=1.0,fixed=1.78; org.bouncycastle:bcprov-jdk15to18 (Maven) ECOSYSTEM:introduced=1.0,fixed=1.78; org.bouncycastle:bcprov-jdk18on (Maven) ECOSYSTEM:introduced=1.0,fixed=1.78; and 3 more.
Is there a fix for CVE-2025-8885?
Yes. org.bouncycastle:bc-fips (Maven): upgrade to 1.0.2.6 or later; org.bouncycastle:bcprov-jdk14 (Maven): upgrade to 1.78 or later; org.bouncycastle:bcprov-jdk15to18 (Maven): upgrade to 1.78 or later; org.bouncycastle:bcprov-jdk18on (Maven): upgrade to 1.78 or later; org.bouncycastle:bctls-jdk14 (Maven): upgrade to 1.78 or later; org.bouncycastle:bctls-jdk15to18 (Maven): upgrade to 1.78 or later; org.bouncycastle:bctls-jdk18on (Maven): upgrade to 1.78 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-8885?
Check whether you run org.bouncycastle:bc-fips (Maven), org.bouncycastle:bcprov-jdk14 (Maven), org.bouncycastle:bcprov-jdk15to18 (Maven) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.bouncycastle:bc-fips (Maven): upgrade to 1.0.2.6 or later
    # set org.bouncycastle:bc-fips to 1.0.2.6 in your pom.xml or build.gradle
  • org.bouncycastle:bcprov-jdk14 (Maven): upgrade to 1.78 or later
    # set org.bouncycastle:bcprov-jdk14 to 1.78 in your pom.xml or build.gradle
  • org.bouncycastle:bcprov-jdk15to18 (Maven): upgrade to 1.78 or later
    # set org.bouncycastle:bcprov-jdk15to18 to 1.78 in your pom.xml or build.gradle
  • org.bouncycastle:bcprov-jdk18on (Maven): upgrade to 1.78 or later
    # set org.bouncycastle:bcprov-jdk18on to 1.78 in your pom.xml or build.gradle
  • org.bouncycastle:bctls-jdk14 (Maven): upgrade to 1.78 or later
    # set org.bouncycastle:bctls-jdk14 to 1.78 in your pom.xml or build.gradle
  • org.bouncycastle:bctls-jdk15to18 (Maven): upgrade to 1.78 or later
    # set org.bouncycastle:bctls-jdk15to18 to 1.78 in your pom.xml or build.gradle
  • org.bouncycastle:bctls-jdk18on (Maven): upgrade to 1.78 or later
    # set org.bouncycastle:bctls-jdk18on to 1.78 in your pom.xml or build.gradle

Affected products

  • org.bouncycastle:bc-fips (Maven) ECOSYSTEM:introduced=1.0.0,fixed=1.0.2.6
  • org.bouncycastle:bcprov-jdk14 (Maven) ECOSYSTEM:introduced=1.0,fixed=1.78
  • org.bouncycastle:bcprov-jdk15to18 (Maven) ECOSYSTEM:introduced=1.0,fixed=1.78
  • org.bouncycastle:bcprov-jdk18on (Maven) ECOSYSTEM:introduced=1.0,fixed=1.78
  • org.bouncycastle:bctls-jdk14 (Maven) ECOSYSTEM:introduced=1.0,fixed=1.78
  • org.bouncycastle:bctls-jdk15to18 (Maven) ECOSYSTEM:introduced=1.0,fixed=1.78
  • org.bouncycastle:bctls-jdk18on (Maven) ECOSYSTEM:introduced=1.0,fixed=1.78

Identifiers

  • CVE-2025-8885
  • GHSA-67mf-3cr5-8w23

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.