Security Resilience

CVE-2026-63575

DoS in Bouncycastle Bc-Csharp ≤ 2.7.0

Published
02 October 2026
Modified
28 October 2026
Patch / advisory
CVSS Score v4 7.1
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0022 13th percentile
Risk Priority 55 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-63575 is a high-severity Infinite Loop (CWE-835) vulnerability in Bouncycastle Bc-Csharp. Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 13th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Loop with unreachable exit condition in the PKCS#12 key derivation (Pkcs12ParametersGenerator) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows an attacker who can supply a PKCS#12 (PFX) file, or a PKCS#8 encrypted private key that uses a…

more

PKCS#12 password-based encryption algorithm, to cause a denial of service through CPU exhaustion via an iteration count of zero or below, because the derivation loop ran until its counter equalled the count, so for such a count it wrapped through about 2^32 iterations before the MAC or the password could be checked. A 75-byte PFX file with a negative MacData iteration count kept Pkcs12Store.Load busy for many minutes.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-63570Same product: Bouncycastle Bc-Csharp
CVE-2026-16001Same product: Bouncycastle Bc-Csharp
CVE-2026-103602Same product: Bouncycastle Bc-Csharp
CVE-2026-103601Same product: Bouncycastle Bc-Csharp
CVE-2026-63566Same product: Bouncycastle Bc-Csharp
CVE-2026-103603Same product: Bouncycastle Bc-Csharp
CVE-2026-15999Same product: Bouncycastle Bc-Csharp
CVE-2026-63573Same product: Bouncycastle Bc-Csharp
CVE-2026-63576Same product: Bouncycastle Bc-Csharp
CVE-2026-63572Same product: Bouncycastle Bc-Csharp

Affected Assets

bouncycastle
bc-csharp
≤ 2.7.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Developer testing and evaluation can discover unreachable loop exit conditions through static analysis, fuzzing, or execution tracing.

Requiring documented development processes and secure coding standards reduces introduction of loops whose termination conditions are unreachable.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices (reviews, testing, static analysis) directly prevent introduction of infinite-loop defects.

ID.RA-01 partial match
blocks

Static analysis and vuln scanning during asset assessment can detect unreachable loop exits.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing can uncover infinite-loop conditions before release.

prevents

Secure coding standards directly address loop termination and prevent infinite loops.

finds

A.8.8's reach is DISCLOSURE — it sees only third-party components with published advisories. CWE-835 instances that surface as CVEs in third-party libraries (e.g., CVE-2025-32399, CVE-2022-25304) are discoverable through vulnerability scanning, but the majority of infinite loops live in first-party code where no advisory is ever published, and A.8.8 has no view of those.

References