What is CVE-2025-8916?

CVE-2025-8916 is a medium-severity allocation of resources without limits or throttling vulnerability in org.bouncycastle:bcpkix-fips (maven), affecting versions >= 1.0.0, <= 1.0.7. It is fixed in 1.0.8, 2.0.8, 1.79. 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-8916?

org.bouncycastle:bcpkix-fips (maven) versions >= 1.0.0, = 1.44, = 1.44, = 1.44, < 1.79.

Is there a fix for CVE-2025-8916?

Yes. CVE-2025-8916 is fixed in 1.0.8, 2.0.8, 1.79. Upgrade to this version or later.

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

Whether CVE-2025-8916 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-8916 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-8916 in org.bouncycastle:bcpkix-fips

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

org.bouncycastle:bcpkix-fips (maven) versions >= 1.0.0, = 1.44, = 1.44, = 1.44, < 1.79.

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

Yes. CVE-2025-8916 is fixed in 1.0.8, 2.0.8, 1.79. Upgrade to this version or later.

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

Whether CVE-2025-8916 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-8916 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-8916?

Upgrade: org.bouncycastle:bcpkix-fips to 1.0.8 or later, org.bouncycastle:bcpkix-fips to 2.0.8 or later, org.bouncycastle:bcpkix-jdk15on to 1.79 or later, org.bouncycastle:bcpkix-jdk15to18 to 1.79 or later, org.bouncycastle:bcpkix-jdk18on to 1.79 or later.

Summary

Bouncy Castle for Java bcpkix, bcprov, bcpkix-fips on All (API modules) allows Excessive Allocation

Allocation of Resources Without Limits or Throttling vulnerability in Legion of the Bouncy Castle Inc. Bouncy Castle for Java bcpkix, bcprov, bcpkix-fips on All (API modules) allows Excessive Allocation. This vulnerability is associated with program files https://github.Com/bcgit/bc-java/blob/main/pkix/src/main/java/org/bouncycastle/pkix/jcajce/PKIXCertP... https://github.Com/bcgit/bc-java/blob/main/pkix/src/main/java/org/bouncycastle/pkix/jcajce/PKIXCertPathReviewer.java , https://github.Com/bcgit/bc-java/blob/main/prov/src/main/java/org/bouncycastle/x509/PKIXCertPathRevi... https://github.Com/bcgit/bc-java/blob/main/prov/src/main/java/org/bouncycastle/x509/PKIXCertPathReviewer.java .

This issue affects Bouncy Castle for Java: from BC 1.44 through 1.78, from BCPKIX FIPS 1.0.0 through 1.0.7, from BCPKIX FIPS 2.0.0 through 2.0.7.

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:bcpkix-fips (>= 1.0.0, <= 1.0.7) org.bouncycastle:bcpkix-fips (>= 2.0.0, <= 2.0.7) org.bouncycastle:bcpkix-jdk15on (>= 1.44, < 1.79) org.bouncycastle:bcpkix-jdk15to18 (>= 1.44, < 1.79) org.bouncycastle:bcpkix-jdk18on (>= 1.44, < 1.79)

Security releases

org.bouncycastle:bcpkix-fips → 1.0.8 (maven) org.bouncycastle:bcpkix-fips → 2.0.8 (maven) org.bouncycastle:bcpkix-jdk15on → 1.79 (maven) org.bouncycastle:bcpkix-jdk15to18 → 1.79 (maven) org.bouncycastle:bcpkix-jdk18on → 1.79 (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:bcpkix-fips to 1.0.8 or later; org.bouncycastle:bcpkix-fips to 2.0.8 or later; org.bouncycastle:bcpkix-jdk15on to 1.79 or later; org.bouncycastle:bcpkix-jdk15to18 to 1.79 or later; org.bouncycastle:bcpkix-jdk18on to 1.79 or later

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

Frequently Asked Questions

What is CVE-2025-8916? CVE-2025-8916 is a medium-severity allocation of resources without limits or throttling vulnerability in org.bouncycastle:bcpkix-fips (maven), affecting versions >= 1.0.0, <= 1.0.7. It is fixed in 1.0.8, 2.0.8, 1.79. 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-8916?
- org.bouncycastle:bcpkix-fips (maven) (versions >= 1.0.0, <= 1.0.7)
- org.bouncycastle:bcpkix-jdk15on (maven) (versions >= 1.44, < 1.79)
- org.bouncycastle:bcpkix-jdk15to18 (maven) (versions >= 1.44, < 1.79)
- org.bouncycastle:bcpkix-jdk18on (maven) (versions >= 1.44, < 1.79)
Is there a fix for CVE-2025-8916? Yes. CVE-2025-8916 is fixed in 1.0.8, 2.0.8, 1.79. Upgrade to this version or later.
Is CVE-2025-8916 exploitable, and should I be worried? Whether CVE-2025-8916 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-8916 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-8916?
- Upgrade org.bouncycastle:bcpkix-fips to 1.0.8 or later
- Upgrade org.bouncycastle:bcpkix-fips to 2.0.8 or later
- Upgrade org.bouncycastle:bcpkix-jdk15on to 1.79 or later
- Upgrade org.bouncycastle:bcpkix-jdk15to18 to 1.79 or later
- Upgrade org.bouncycastle:bcpkix-jdk18on to 1.79 or later