How severe is CVE-2025-8885?

No CVSS score has been assigned to CVE-2025-8885 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-8885?

CVE-2025-8885 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 CVE-2025-8885?

Update org.bouncycastle:bcprov-jdk14 to 1.78 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-8885 is resolved across your whole dependency graph.

How do I detect CVE-2025-8885 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 CVE-2025-8885 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2025-8885 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-8885 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 CVE-2025-8885?

CVE-2025-8885 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 48th 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 CVE-2025-8885?

CVE-2025-8885 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 CVE-2025-8885 published, and has it been updated?

CVE-2025-8885 was published on August 12, 2025 and was last updated on October 28, 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

CVE-2025-8885 — bcprov-jdk14

Fix: bcgit/bc-java@3790993

CVE-2025-8885 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.

Possible DOS in processing specially formed ASN.1 Object Identifiers

Also known asGHSA-67mf-3cr5-8w23

Published

Aug 12, 2025

Updated

Oct 28, 2026

Affected

8 pkgs

Patched

8 / 8

Exploits

None indexed

Exploitation data as of Nov 4, 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 CVE-2025-8885.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk+0.05%

Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

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 CVE-2025-8885 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2025-8885 (CC BY 4.0)

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 CVE-2025-8885 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works