Bouncy Castle for Java has Uncontrolled Resource Consumption Vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:N/R:U/V:C/RE:M/U:Amber · score source

EPSS

• CVE-2025-9341: 0.16% estimated exploitation activity in the next 30 days; percentile 5.19 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Uncontrolled Resource Consumption vulnerability in Legion of the Bouncy Castle Inc. Bouncy Castle for Java FIPS bc-fips on All (API modules) allows Excessive Allocation. This vulnerability is associated with program files org/bouncycastle/crypto/fips/AESNativeCBC.Java. This issue affects Bouncy Castle for Java FIPS: from BC-FJA 2.1.0 through 2.1.0.

Published by the source

22 Aug 2025, 09:30 UTC

Last modified by the source

22 Aug 2025, 20:30 UTC

Source last checked

26 Oct 2026, 16:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jfcv-jv9g-2vx2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-9341

Advisory: Bouncy Castle for Java has Uncontrolled Resource Consumption Vulnerability
IDs: CVE-2025-9341, GHSA-jfcv-jv9g-2vx2
Record: https://patchnext.com/advisories/cve-2025-9341 (revision 1, source checked 26 Oct 2026, 16:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.bouncycastle:bc-fips 2.1.1; org.bouncycastle:bctls-fips 2.73.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.bouncycastle:bc-fips: affected >= 2.1.0, <= 2.1.0; fixed in 2.1.1
- Maven org.bouncycastle:bctls-fips: affected >= 2.73.7, <= 2.73.7; fixed in 2.73.8

## Suggested inspection (read-only)
- Maven org.bouncycastle:bc-fips: check the installed version with your package manager.
- Maven org.bouncycastle:bctls-fips: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.bouncycastle:bc-fips, org.bouncycastle:bctls-fips.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jfcv-jv9g-2vx2 (GitHub-reviewed advisory GHSA-jfcv-jv9g-2vx2 lists affected ranges: Maven org.bouncycastle:bc-fips >=2.1.0 =2.73.7 <=2.73.7)

Commands are suggestions: review each one before running it.