CVE-2025-8916: Possible DOS in processing large name constraint structures in PKIXCertPathReveiwer
Allocation of Resources Without Limits or Throttling vulnerability in Legion of the Bouncy Castle Inc. BC Java bcpkix on All (API modules), Legion of the Bouncy Castle Inc. BC Java bcprov on All (API modules), Legion of the Bouncy Castle Inc. BCPKIX FIPS bcpkix-fips on All (API modules) allows Excessive Allocation. This vulnerability is associated with program files https://github.Com/bcgit/bc-java/blob/main/pkix/src/main/java/org/bouncycastle/pkix/jcajce/PKIXCertPathReviewer.Java, https://github.Com/bcgit/bc-java/blob/main/prov/src/main/java/org/bouncycastle/x509/PKIXCertPathReviewer.Java.
This issue affects BC Java: from 1.44 through 1.78; BC Java: from 1.44 through 1.78; BCPKIX FIPS: from 1.0.0 through 1.0.7, from 2.0.0 through 2.0.7.
Security readout for executives and security teams
Plain-English summary
This is a denial-of-service risk in Bouncy Castle Java certificate path review code. A specially large certificate name-constraint structure can cause excessive resource allocation. Business impact is availability, not data theft or tampering, based on the provided CVSS vector.
Executive priority
Treat as a moderate availability issue. Prioritize systems that validate customer, partner, device, or internet-supplied certificates. It does not currently justify emergency response unless a critical service depends on affected versions and accepts untrusted certificate material.
Technical view
CVE-2025-8916 is CWE-770 in BC Java bcpkix and bcprov API modules and BCPKIX FIPS bcpkix-fips. It affects PKIXCertPathReviewer processing of large name constraint structures, allowing excessive allocation. Reported affected ranges are BC Java 1.44 through 1.78, and BCPKIX FIPS 1.0.0-1.0.7 and 2.0.0-2.0.7.
Likely exposure
Exposure is most likely where applications accept or validate externally supplied certificate chains using affected Bouncy Castle PKIX reviewer APIs. Internet-reachable services doing certificate validation have higher availability concern. Evidence does not show confidentiality or integrity impact.
Exploitation context
The CVE record rates attack vector as network, low complexity, no privileges, no user interaction, with present attack requirements and low availability impact. KEV is false in the provided bundle, so active exploitation is not established here.
Researcher notes
The source bundle identifies affected files but does not include exploit details, patch diffs, or confirmed fixed versions. Avoid assuming all Bouncy Castle usage is reachable; validate whether PKIXCertPathReviewer paths process attacker-controlled certificate chains.
Mitigation direction
Identify Bouncy Castle bcpkix, bcprov, and bcpkix-fips versions in deployed applications.
Check Bouncy Castle vendor guidance for fixed versions or recommended mitigations.
Prioritize internet-facing certificate validation paths and services with strict uptime requirements.
Update Siemens-affected products according to the Siemens advisory where applicable.
Apply operational rate limits or isolation around untrusted certificate-processing workflows where feasible.
Validation and detection
Inventory Java dependencies and transitive dependencies for bcpkix, bcprov, and bcpkix-fips.
Compare discovered versions against the affected ranges listed in the CVE record.
Map where applications invoke PKIX certificate path review on untrusted certificate chains.
Review logs and metrics for certificate-validation memory spikes or availability degradation.
Confirm vendor advisory status before marking patched or unaffected.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-770 · source CWE mapping
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.