What is CVE-2025-9092?

CVE-2025-9092 is a low-severity uncontrolled resource consumption vulnerability in org.bouncycastle:bc-fips (maven), affecting versions = 2.1.0. It is fixed in 2.1.1. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

Which versions of org.bouncycastle:bc-fips are affected by CVE-2025-9092?

org.bouncycastle:bc-fips (maven) versions = 2.1.0 is affected.

Is there a fix for CVE-2025-9092?

Yes. CVE-2025-9092 is fixed in 2.1.1. Upgrade to this version or later.

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

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

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

Upgrade org.bouncycastle:bc-fips to 2.1.1 or later.

Summary

Bouncy Castle for Java Uncontrolled Resource Consumption Vulnerability

Uncontrolled Resource Consumption vulnerability in Legion of the Bouncy Castle Inc. Bouncy Castle for Java - BC-FJA 2.1.0 bc-fips (API modules) allows Excessive Allocation. This vulnerability is associated with program files org.Bouncycastle.Crypto.Fips.NativeLoader.

This issue affects Bouncy Castle for Java - BC-FJA 2.1.0: from BC-FJA 2.1.0 through 2.1.0.

Impact

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

Affected versions

org.bouncycastle:bc-fips (= 2.1.0)

Security releases

org.bouncycastle:bc-fips → 2.1.1 (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 org.bouncycastle:bc-fips to 2.1.1 or later to resolve this vulnerability.

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

Frequently Asked Questions

What is CVE-2025-9092? CVE-2025-9092 is a low-severity uncontrolled resource consumption vulnerability in org.bouncycastle:bc-fips (maven), affecting versions = 2.1.0. It is fixed in 2.1.1. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
Which versions of org.bouncycastle:bc-fips are affected by CVE-2025-9092? org.bouncycastle:bc-fips (maven) versions = 2.1.0 is affected.
Is there a fix for CVE-2025-9092? Yes. CVE-2025-9092 is fixed in 2.1.1. Upgrade to this version or later.
Is CVE-2025-9092 exploitable, and should I be worried? Whether CVE-2025-9092 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-9092 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-9092? Upgrade org.bouncycastle:bc-fips to 2.1.1 or later.

Other vulnerabilities in org.bouncycastle:bc-fips

CVE-IDSeverityPackage summary

CVE-2025-12194Mediumorg.bouncycastle:bc-fips: Bouncy Castle Vulnerable to Uncontrolled Resource Consumption CVE-2025-9340Loworg.bouncycastle:bc-fips: Bouncy Castle for Java has Out-of-Bounds Write Vulnerability CVE-2025-9341Mediumorg.bouncycastle:bc-fips: Bouncy Castle for Java has Uncontrolled Resource Consumption Vulnerability CVE-2025-8885Mediumorg.bouncycastle:bcprov-jdk14: Bouncy Castle for Java on All (API modules) allows Excessive Allocation CVE-2024-29857Mediumorg.bouncycastle:bcprov-jdk18on: Bouncy Castle certificate parsing issues cause high CPU usage during parameter evaluation.