Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-jv6h-4262-q663

Bouncy Castle Vulnerable to Uncontrolled Resource Consumption

CVSS 5.9 MediumEPSS 0.0016 · 4th percentile

Published by the GitHub Advisory Database at 25 Oct 2025, 00:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.bouncycastle:bc-fipsMaven>=2.1.0, <2.1.22.1.2
org.bouncycastle:bcprov-debug-lts8onMaven>=2.73.0, <2.73.82.73.8
Identifiers
GHSA-jv6h-4262-q663 · CVE-2025-12194
Weakness (CWE)
CWE-400
Tags
Published
25 Oct 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Bouncy Castle for Java: the bc-fips package (Maven org.bouncycastle:bc-fips) versions 2.1.0 through 2.1.1 and the bcprov-lts8on package (Maven org.bouncycastle:bcprov-debug-lts8on) versions 2.73.0 through 2.73.7 are affected by an uncontrolled resource consumption flaw that allows excessive memory allocation in the native AES and SHA digest classes. The source does not describe what an attacker must do to trigger it. Upgrade bc-fips to 2.1.2 or bcprov-debug-lts8on to 2.73.8.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.9 Medium 4.0 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 CNA (bcorg)
  • CISA KEV Not listed.
  • EPSS 0.0016, the 4th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.