CVE Tools

CVE-2025-9341

Garbage collection can delay for AES CBC Native support, resulting in heap exhaustion

No known exploitation. EPSS puts it in the 6th percentile. Fixed versions are out.

Check it yourself

No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.

Request a scan

Published Updated Sources: CVE.org, NVD, GitHub

What to do

Find your product and version, then upgrade to the build on the right.

  • Legion of the Bouncy Castle Inc. Bouncy Castle for Java FIPSAffected: 2.1.0Upgrade to: not statedStated by: CVE record
  • Legion of the Bouncy Castle Inc. Bouncy Castle for Java LTSAffected: ≥ 2.73.0, ≤ 2.73.7Upgrade to: after 2.73.7Stated by: CVE record
  • Maven org.bouncycastle:bc-fipsAffected: ≥ 2.1.0, < 2.1.1Upgrade to: 2.1.1Stated by: GitHub advisory
  • Maven org.bouncycastle:bctls-fipsAffected: ≥ 2.73.7, < 2.73.8Upgrade to: 2.73.8Stated by: GitHub advisory

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

Bouncy Castle for Java has Uncontrolled Resource Consumption Vulnerability

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS6th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.2% chance of exploitation activity in the next 30 days, which ranks it in the 6th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 63 days, from the signal feeds we watch.

  1. Patch availableworkaround available, record updated
  2. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Org.bouncycastle:bc-fips, not every advisory.