What is CVE-2025-8885?

CVE-2025-8885 is a medium-severity allocation of resources without limits or throttling vulnerability in org.bouncycastle:bcprov-jdk14 (maven), affecting versions >= 1.0, < 1.78. It is fixed in 1.78, 2.0.1, 1.0.2.6. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.

Which packages are affected by CVE-2025-8885?

org.bouncycastle:bcprov-jdk14 (maven) versions >= 1.0, = 1.0, = 1.0, = 1.0, = 1.0, = 1.0, < 1.78; org.bouncycastle:bc-fips (maven) versions = 2.0.0.

Is there a fix for CVE-2025-8885?

Yes. CVE-2025-8885 is fixed in 1.78, 2.0.1, 1.0.2.6. Upgrade to this version or later.

Is CVE-2025-8885 exploitable, and should I be worried?

Whether CVE-2025-8885 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-8885 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-8885 in org.bouncycastle:bcprov-jdk14

Q: Which packages are affected by CVE-2025-8885?

org.bouncycastle:bcprov-jdk14 (maven) versions >= 1.0, = 1.0, = 1.0, = 1.0, = 1.0, = 1.0, < 1.78; org.bouncycastle:bc-fips (maven) versions = 2.0.0.

Q: Is there a fix for CVE-2025-8885?

Yes. CVE-2025-8885 is fixed in 1.78, 2.0.1, 1.0.2.6. Upgrade to this version or later.

Q: Is CVE-2025-8885 exploitable, and should I be worried?

Whether CVE-2025-8885 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-8885 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-8885?

Upgrade: org.bouncycastle:bcprov-jdk14 to 1.78 or later, org.bouncycastle:bcprov-jdk15to18 to 1.78 or later, org.bouncycastle:bcprov-jdk18on to 1.78 or later, org.bouncycastle:bctls-jdk14 to 1.78 or later, org.bouncycastle:bctls-jdk15to18 to 1.78 or later, org.bouncycastle:bctls-jdk18on to 1.78 or later, org.bouncycastle:bc-fips to 2.0.1 or later, org.bouncycastle:bc-fips to 1.0.2.6 or later.

Summary

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

A resource allocation vulnerability exists in Bouncy Castle for Java (by Legion of the Bouncy Castle Inc.) that affects all API modules. The vulnerability allows attackers to cause excessive memory allocation through unbounded resource consumption, potentially leading to denial of service. The issue is located in the ASN1ObjectIdentifier.java file in the core module.

This issue affects Bouncy Castle for Java: from BC 1.0 through 1.77, from BC-FJA 1.0.0 through 2.0.0.

Impact

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

Affected versions

org.bouncycastle:bcprov-jdk14 (>= 1.0, < 1.78) org.bouncycastle:bcprov-jdk15to18 (>= 1.0, < 1.78) org.bouncycastle:bcprov-jdk18on (>= 1.0, < 1.78) org.bouncycastle:bctls-jdk14 (>= 1.0, < 1.78) org.bouncycastle:bctls-jdk15to18 (>= 1.0, < 1.78) org.bouncycastle:bctls-jdk18on (>= 1.0, < 1.78) org.bouncycastle:bc-fips (= 2.0.0) org.bouncycastle:bc-fips (>= 1.0.0, < 1.0.2.6)

Security releases

org.bouncycastle:bcprov-jdk14 → 1.78 (maven) org.bouncycastle:bcprov-jdk15to18 → 1.78 (maven) org.bouncycastle:bcprov-jdk18on → 1.78 (maven) org.bouncycastle:bctls-jdk14 → 1.78 (maven) org.bouncycastle:bctls-jdk15to18 → 1.78 (maven) org.bouncycastle:bctls-jdk18on → 1.78 (maven) org.bouncycastle:bc-fips → 2.0.1 (maven) org.bouncycastle:bc-fips → 1.0.2.6 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.bouncycastle:bcprov-jdk14 to 1.78 or later; org.bouncycastle:bcprov-jdk15to18 to 1.78 or later; org.bouncycastle:bcprov-jdk18on to 1.78 or later; org.bouncycastle:bctls-jdk14 to 1.78 or later; org.bouncycastle:bctls-jdk15to18 to 1.78 or later; org.bouncycastle:bctls-jdk18on to 1.78 or later; org.bouncycastle:bc-fips to 2.0.1 or later; org.bouncycastle:bc-fips to 1.0.2.6 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-8885? CVE-2025-8885 is a medium-severity allocation of resources without limits or throttling vulnerability in org.bouncycastle:bcprov-jdk14 (maven), affecting versions >= 1.0, < 1.78. It is fixed in 1.78, 2.0.1, 1.0.2.6. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
Which packages are affected by CVE-2025-8885?
- org.bouncycastle:bcprov-jdk14 (maven) (versions >= 1.0, < 1.78)
- org.bouncycastle:bcprov-jdk15to18 (maven) (versions >= 1.0, < 1.78)
- org.bouncycastle:bcprov-jdk18on (maven) (versions >= 1.0, < 1.78)
- org.bouncycastle:bctls-jdk14 (maven) (versions >= 1.0, < 1.78)
- org.bouncycastle:bctls-jdk15to18 (maven) (versions >= 1.0, < 1.78)
- org.bouncycastle:bctls-jdk18on (maven) (versions >= 1.0, < 1.78)
- org.bouncycastle:bc-fips (maven) (versions = 2.0.0)
Is there a fix for CVE-2025-8885? Yes. CVE-2025-8885 is fixed in 1.78, 2.0.1, 1.0.2.6. Upgrade to this version or later.
Is CVE-2025-8885 exploitable, and should I be worried? Whether CVE-2025-8885 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-8885 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-8885?
- Upgrade org.bouncycastle:bcprov-jdk14 to 1.78 or later
- Upgrade org.bouncycastle:bcprov-jdk15to18 to 1.78 or later
- Upgrade org.bouncycastle:bcprov-jdk18on to 1.78 or later
- Upgrade org.bouncycastle:bctls-jdk14 to 1.78 or later
- Upgrade org.bouncycastle:bctls-jdk15to18 to 1.78 or later
- Upgrade org.bouncycastle:bctls-jdk18on to 1.78 or later
- Upgrade org.bouncycastle:bc-fips to 2.0.1 or later
- Upgrade org.bouncycastle:bc-fips to 1.0.2.6 or later

Other vulnerabilities in org.bouncycastle:bcprov-jdk14

CVE-IDSeverityPackage summary

CVE-2026-5598Highorg.bouncycastle:bcprov-jdk15to18: Bouncy Castle Has Covert Timing Channel Vulnerability CVE-2026-0636Mediumorg.bouncycastle:bcprov-jdk14: Bouncy Castle has an LDAP injection CVE-2025-14813Criticalorg.bouncycastle:bcprov-jdk14: Bouncy Castle for Java GOST 28147 CTR mode reuses keystream after 255 blocks CVE-2024-30171Mediumorg.bouncycastle:bctls-fips: Bouncy Castle affected by timing side-channel for RSA key exchange ("The Marvin Attack")CVE-2024-30172MediumBouncyCastle: Bouncy Castle crafted signature and public key can be used to trigger an infinite loop