CVE-2026-58060
Received Received - Intake

Bouncy Castle Java HSS Public Key Allocation Flaw

Publication date: 2026-08-03

Last updated on: 2026-08-03

Assigner: bcorg

Description
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) and 2.1.3 (2.1.X series).

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-03
Last Modified
2026-08-03
Generated
2026-08-03
AI Q&A
2026-08-03
EPSS Evaluated
N/A
NVD
CVE-2026-58060
EUVD
EUVD-2026-52091

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
bouncy_castle bouncy_castle to 1.85 (exc)
bouncy_castle bouncy_castle_lts to 2.73.12 (exc)
bouncy_castle bc_fips to 2.0.2 (exc)
bouncy_castle bc_fips to 2.1.3 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-789 The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Bouncy Castle for Java involves an unbounded HSS public-key level count during verification, leading to excessive memory allocation. It affects multiple versions including Java before 1.85, LTS before 2.73.12, and FIPS versions before bc-fips 2.0.2 and 2.1.3.

Detection Guidance

Detection involves checking the Bouncy Castle library version in use. Commands like 'mvn dependency:tree' for Maven projects or 'gradle dependencies' for Gradle projects can help identify the version. Compare the version against the patched releases (Java 1.85+, LTS 2.73.12+, BC-FJA 2.0.2/2.1.3+).

Impact Analysis

This flaw could cause denial-of-service by consuming excessive system resources during cryptographic verification. Attackers might exploit it to crash applications or services relying on Bouncy Castle for Java.

Compliance Impact

This vulnerability involves unbounded HSS public-key level count leading to huge allocation during verification, which could cause denial-of-service conditions. Such resource exhaustion may impact availability of systems handling sensitive data, potentially violating compliance requirements for availability in standards like GDPR (data integrity and availability) and HIPAA (system availability and integrity).

Mitigation Strategies

Upgrade Bouncy Castle for Java to version 1.85 or later. For LTS versions, upgrade to 2.73.12 or later. For BC-FJA, upgrade to bc-fips 2.0.2 (2.0.X series) or 2.1.3 (2.1.X series).

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-58060. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart