Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-67mf-3cr5-8w23

Bouncy Castle for Java on All (API modules) allows Excessive Allocation

CVSS 6.3 MediumEPSS 0.0063 · 51st percentile

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

PackageEcosystemAffectedFixed in
org.bouncycastle:bcprov-jdk14Maven>=1.0, <1.781.78
org.bouncycastle:bcprov-jdk15to18Maven>=1.0, <1.781.78
org.bouncycastle:bcprov-jdk18onMaven>=1.0, <1.781.78
org.bouncycastle:bctls-jdk14Maven>=1.0, <1.781.78
org.bouncycastle:bctls-jdk15to18Maven>=1.0, <1.781.78
org.bouncycastle:bctls-jdk18onMaven>=1.0, <1.781.78
org.bouncycastle:bc-fipsMaven>=1.0.0, <1.0.2.6 || >=2.0.0, <2.0.11.0.2.6, 2.0.1
Identifiers
GHSA-67mf-3cr5-8w23 · CVE-2025-8885
Weakness (CWE)
CWE-770
Tags
Published
12 Aug 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 API modules (bcprov, bctls and bc-fips packages, versions before 1.78 for the first two and before 1.0.2.6 or 2.0.1 for bc-fips) allow excessive memory allocation through unbounded resource consumption. An attacker who can supply input that is parsed as an ASN.1 object identifier may trigger a denial of service. Upgrade to 1.78 for the bcprov and bctls packages, or to 1.0.2.6 or 2.0.1 for bc-fips, as applicable. The source gives few details about the exact attack conditions.

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
6.3 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/S:P/R:U/RE:M/U:Amber CNA (bcorg)
  • CISA KEV Not listed.
  • EPSS 0.0063, the 51st percentile, on 13 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.