How severe is GHSA-67mf-3cr5-8w23?

No CVSS score has been assigned to GHSA-67mf-3cr5-8w23 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-67mf-3cr5-8w23?

GHSA-67mf-3cr5-8w23 affects the following packages: org.bouncycastle:bcprov-jdk14 (Maven), org.bouncycastle:bcprov-jdk15to18 (Maven), org.bouncycastle:bcprov-jdk18on (Maven), org.bouncycastle:bctls-jdk14 (Maven), org.bouncycastle:bctls-jdk15to18 (Maven), org.bouncycastle:bctls-jdk18on (Maven), org.bouncycastle:bc-fips (Maven), org.bouncycastle:bc-fips (Maven). Ecosystems affected: Maven.

How do I fix GHSA-67mf-3cr5-8w23?

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.

How do I detect GHSA-67mf-3cr5-8w23 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.bouncycastle:bcprov-jdk14, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-67mf-3cr5-8w23 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-67mf-3cr5-8w23?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-67mf-3cr5-8w23 can be triaged on real exposure rather than presence alone.

Is GHSA-67mf-3cr5-8w23 actively exploited in the wild?

No public exploit code has been indexed for GHSA-67mf-3cr5-8w23 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-67mf-3cr5-8w23?

GHSA-67mf-3cr5-8w23 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 43th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-67mf-3cr5-8w23?

GHSA-67mf-3cr5-8w23 is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-67mf-3cr5-8w23 published, and has it been updated?

GHSA-67mf-3cr5-8w23 was published on August 12, 2025 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

GHSA-67mf-3cr5-8w23 — bcprov-jdk14

Fix: bcgit/bc-java@3790993

GHSA-67mf-3cr5-8w23 is a CWE-770 vulnerability in org.bouncycastle:bcprov-jdk14. A fix is available for org.bouncycastle:bcprov-jdk14 — see the affected versions and patch details below.

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

Also known asCVE-2025-8885

Published

Aug 12, 2025

Updated

Sep 10, 2026

Affected

8 pkgs

Patched

8 / 8

Exploits

None indexed

Exploitation data as of Sep 25, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-67mf-3cr5-8w23.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

8 pkgs affected

☕org.bouncycastle:bcprov-jdk14☕org.bouncycastle:bcprov-jdk15to18☕org.bouncycastle:bcprov-jdk18on☕org.bouncycastle:bctls-jdk14☕org.bouncycastle:bctls-jdk15to18☕org.bouncycastle:bctls-jdk18on☕org.bouncycastle:bc-fips☕org.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

Allocation of Resources Without Limits or Throttling vulnerability in Legion of the Bouncy Castle Inc. BC Java bcprov on All (API modules), Legion of the Bouncy Castle Inc. BC-FJA bc-fips on All allows Excessive Allocation. This vulnerability is associated with program files https://github.com/bcgit/bc-java/blob/main/core/src/main/java/org/bouncycastle/asn1/ASN1ObjectIdenti... https://github.com/bcgit/bc-java/blob/main/core/src/main/java/org/bouncycastle/asn1/ASN1ObjectIdentifier.Java .

This issue affects BC Java: from 1.0 through 1.77; BC-FJA: from 1.0.0 through 1.0.2.5, from 2.0.0 through 2.0.1.

Affected Packages

8 total 8 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.bouncycastle:bcprov-jdk14`	≥ 1.0&&< 1.78	1.78`org.bouncycastle:bcprov-jdk14:1.78`
☕Maven	`org.bouncycastle:bcprov-jdk15to18`	≥ 1.0&&< 1.78	1.78`org.bouncycastle:bcprov-jdk15to18:1.78`
☕Maven	`org.bouncycastle:bcprov-jdk18on`	≥ 1.0&&< 1.78	1.78`org.bouncycastle:bcprov-jdk18on:1.78`
☕Maven	`org.bouncycastle:bctls-jdk14`	≥ 1.0&&< 1.78	1.78`org.bouncycastle:bctls-jdk14:1.78`
☕Maven	`org.bouncycastle:bctls-jdk15to18`	≥ 1.0&&< 1.78	1.78`org.bouncycastle:bctls-jdk15to18:1.78`
☕Maven	`org.bouncycastle:bctls-jdk18on`	≥ 1.0&&< 1.78	1.78`org.bouncycastle:bctls-jdk18on:1.78`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.bouncycastle:bcprov-jdk14, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-67mf-3cr5-8w23 can be triaged on real exposure rather than presence alone.

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 Security finds GHSA-67mf-3cr5-8w23 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works