Security Resilience

CVE-2026-58060

Bouncycastle Bc-Java 1.65 – 1.85

Published
03 August 2026
Modified
02 September 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.0065 52th 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-58060 is a high-severity Memory Allocation with Excessive Size Value (CWE-789) vulnerability in Bouncycastle Bc-Java. Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) 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, HSS public-key level count unbounded, enabling huge allocation on verify. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 2.0.2 (2.0.X series)…

more

and 2.1.3 (2.1.X series).

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.
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-14682Same product: Bouncycastle Bc-Java
CVE-2026-12185Same product: Bouncycastle Bc-Java
CVE-2026-59649Same product: Bouncycastle Bc-Java
CVE-2026-59646Same product: Bouncycastle Bc-Java
CVE-2026-12852Same product: Bouncycastle Bc-Java
CVE-2026-58063Same product: Bouncycastle Bc-Java
CVE-2026-13586Same product: Bouncycastle Bc-Java
CVE-2026-58061Same product: Bouncycastle Bc-Java
CVE-2026-63574Same vendor: Bouncycastle
CVE-2026-8763Same product: Bouncycastle Bc-Java

Affected Assets

bouncycastle
bc-java
1.65 — 1.85
bouncycastle
bouncy castle for java lts
≤ 2.73.11
bouncycastle
fips java api
≤ 2.0.2 · 2.1.0 — 2.1.3

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Input validation directly rejects or bounds untrusted size values before any allocation occurs.

Resource quotas and priority allocation limit the system-wide impact of an oversized request.

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 directly prevent coding flaws that trust unvalidated size values for allocations.

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 in development can detect and block excessive allocation flaws before deployment.

prevents

Training technical teams on secure coding practices (the education/training portion of A.6.3) can reduce instances of unchecked memory allocation by raising developer awareness of input validation for size values, but the effect is a minority one — the same human-practice ceiling that caps A.8.28 on CWE-502 and CWE-79, and that graded A.6.3 partial on CWE-598.

prevents

Secure coding standards directly prohibit allocating memory from untrusted size values without validation.

prevents

A.8.30 carries its preventive effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation defects like CWE-789 in delivered code the way those practices do, at `partial` -- the clause's ceiling on this verb.

finds

A.8.8's reach is disclosure-based (vulnerability scanning, published advisories, component inventory); CWE-789 does surface as CVEs (multiple observed examples), so the disclosed minority is found, but most instances in first-party or un-disclosed code are outside A.8.8's view.

References