Security Resilience

CVE-2026-59644

DoS in Bouncycastle Bc-Java ≤ 1.85

Published
03 August 2026
Modified
23 October 2026
Patch / advisory
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/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:Amber
EPSS Score 0.0049 43th percentile
Risk Priority 45 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-59644 is a high-severity Excessive Iteration (CWE-834) vulnerability in Bouncycastle Bc-Java. Its CVSS base score is 8.7 (High).

Operationally, ranked at the 43th 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-8 (Security and Privacy Engineering Principles) and SC-6 (Resource Availability) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

In Bouncy Castle for Java before 1.85, MLS hash-ratchet honours arbitrary 32-bit generation counter from sender.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-12852Same product: Bouncycastle Bc-Java
CVE-2023-33201Same product: Bouncycastle Bc-Java
CVE-2026-17507Same product: Bouncycastle Bc-Java
CVE-2024-14041Same product: Bouncycastle Bc-Java
CVE-2026-59652Same product: Bouncycastle Bc-Java
CVE-2026-59651Same product: Bouncycastle Bc-Java
CVE-2026-59643Same product: Bouncycastle Bc-Java
CVE-2026-12185Same product: Bouncycastle Bc-Java
CVE-2026-12860Same product: Bouncycastle Bc-Java
CVE-2026-12816Same product: Bouncycastle Bc-Java

Affected Assets

bouncycastle
bc-java
≤ 1.85

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Engineering principles can require developers to bound all loops and iterations at design time.

Resource quotas limit the CPU/time impact of an excessively long loop without eliminating the flaw.

Input validation can reject or sanitize data that would otherwise drive unbounded iteration.

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 detect excessive iteration through stress and fuzz testing.

prevents

Secure coding standards explicitly forbid unbounded loops and require explicit iteration limits.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-834, a class-level weakness, and none of its children carries one either.

References