# CVE-2025-9341: Garbage collection can delay for AES CBC Native support, resulting in heap exhaustion

> Attackers can cause heap exhaustion and denial of service in Bouncy Castle Java libraries via delayed garbage collection in AES CBC native support.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/S:P/AU:N/R:U/V:C/RE:M/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Aug 2025
- **Updated:** 24 Oct 2025
- **Also known as:** GHSA-jfcv-jv9g-2vx2

## What is CVE-2025-9341?

CVE-2025-9341 is a medium-severity denial of service vulnerability in Legion of the Bouncy Castle Inc. Bouncy Castle for Java FIPS, published on 22 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Uncontrolled Resource Consumption vulnerability in Legion of the Bouncy Castle Inc. Bouncy Castle for Java FIPS bc-fips on All (API modules), Legion of the Bouncy Castle Inc. Bouncy Castle for Java LTS bcprov-lts8on on All (API modules) allows Excessive Allocation. This vulnerability is associated with program files org/bouncycastle/crypto/fips/AESNativeCBC.Java, org/bouncycastle/crypto/engines/AESNativeCBC.Java.

This issue affects Bouncy Castle for Java FIPS: 2.1.0; Bouncy Castle for Java LTS: from 2.73.0 through 2.73.7.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2025-9341?

4 open source packages ship an affected version, including org.bouncycastle:bc-fips and org.bouncycastle:bctls-fips.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.bouncycastle:bc-fips` | Maven | From 2.1.0 | 2.1.1 |
| `org.bouncycastle:bc-fips` | Maven | From 2.1.0 | 2.1.1 |
| `org.bouncycastle:bctls-fips` | Maven | From 2.73.7 | 2.73.8 |
| `org.bouncycastle:bctls-fips` | Maven | From 2.73.7 | 2.73.8 |

## How do I fix CVE-2025-9341?

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

## Is CVE-2025-9341 being exploited?

There is no known exploitation of CVE-2025-9341 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-9341 and fix it if it is affected.

What it is: CVE-2025-9341 is a medium-severity denial of service vulnerability in Legion of the Bouncy Castle Inc. Bouncy Castle for Java FIPS, published on 22 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9341 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.bouncycastle:bc-fips (Maven): affected from 2.1.0; fixed in 2.1.1
- org.bouncycastle:bc-fips (Maven): affected from 2.1.0; fixed in 2.1.1
- org.bouncycastle:bctls-fips (Maven): affected from 2.73.7; fixed in 2.73.8
- org.bouncycastle:bctls-fips (Maven): affected from 2.73.7; fixed in 2.73.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-9341/ (Markdown: https://insights.sbomify.com/CVE-2025-9341/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-9341
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-9341
- OSV: https://osv.dev/vulnerability/CVE-2025-9341

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-9341/
Summaries are generated and may contain mistakes; the official description above is the record.