Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-67mf-3cr5-8w23

Fix: bcgit/bc-java@3790993

GHSA-67mf-3cr5-8w23 is a CWE-770 vulnerability in org.bouncycastle:bcprov-jdk14. O3 Security confirms whether GHSA-67mf-3cr5-8w23 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Also known asCVE-2025-8885
Published
Aug 12, 2025
Updated
Feb 4, 2026
Affected
8 pkgs
Patched
8 / 8
Exploits
None indexed

Real-World Exposure

8 pkgs affected
org.bouncycastle:bcprov-jdk14org.bouncycastle:bcprov-jdk15to18org.bouncycastle:bcprov-jdk18onorg.bouncycastle:bctls-jdk14org.bouncycastle:bctls-jdk15to18org.bouncycastle:bctls-jdk18onorg.bouncycastle:bc-fipsorg.bouncycastle:bc-fips

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

A resource allocation vulnerability exists in Bouncy Castle for Java (by Legion of the Bouncy Castle Inc.) that affects all API modules. The vulnerability allows attackers to cause excessive memory allocation through unbounded resource consumption, potentially leading to denial of service. The issue is located in the ASN1ObjectIdentifier.java file in the core module.

This issue affects Bouncy Castle for Java: from BC 1.0 through 1.77, from BC-FJA 1.0.0 through 2.0.0.

Affected Packages

8 total 8 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.bouncycastle:bcprov-jdk141.0&&< 1.781.78
Mavenorg.bouncycastle:bcprov-jdk15to181.0&&< 1.781.78
Mavenorg.bouncycastle:bcprov-jdk18on1.0&&< 1.781.78
Mavenorg.bouncycastle:bctls-jdk141.0&&< 1.781.78
Mavenorg.bouncycastle:bctls-jdk15to181.0&&< 1.781.78
Mavenorg.bouncycastle:bctls-jdk18on1.0&&< 1.781.78

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.bouncycastle:bcprov-jdk14. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.bouncycastle:bcprov-jdk14 to 1.78 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-67mf-3cr5-8w23 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-67mf-3cr5-8w23 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-67mf-3cr5-8w23. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A resource allocation vulnerability exists in Bouncy Castle for Java (by Legion of the Bouncy Castle Inc.) that affects all API modules. The vulnerability allows attackers to cause excessive memory allocation through unbounded resource consumption, potentially leading to denial of service. The issue is located in the ASN1ObjectIdentifier.java file in the core module. This issue affects Bouncy Castle for Java: from BC 1.0 through 1.77, from BC-FJA 1.0.0 through 2.0.0.
O3 Security · Impact-Aware SCA

Is GHSA-67mf-3cr5-8w23 in your dependencies?

O3 detects GHSA-67mf-3cr5-8w23 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.