CVE-2026-58062 in Bouncy Castle for Java FIPS
Summary
by MITRE • 08/03/2026
In Bouncy Castle for Java before 1.85, Stapled OCSP response accepted without binding to the checked certificate. 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).
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 08/03/2026
The vulnerability in Bouncy Castle for Java represents a critical certificate validation flaw that undermines the integrity of online certificate status protocol ocsp responses. This issue affects multiple versions of the cryptographic library including both standard and long term support releases as well as the fips compliant variant, indicating a widespread problem within the software ecosystem that organizations rely upon for secure communications.
The technical flaw stems from the improper handling of stapled ocsp responses where the system accepts certificate status information without establishing a proper binding relationship between the ocsp response and the certificate being validated. This creates a scenario where an attacker could potentially provide a forged or manipulated ocsp response that would be accepted as valid by the system, effectively bypassing certificate validation mechanisms that are designed to detect revoked or compromised certificates.
This vulnerability directly impacts the security posture of applications using Bouncy Castle for java by weakening certificate validation processes that are fundamental to establishing trust in public key infrastructure pkix environments. The operational impact is significant as it allows malicious actors to potentially present invalid certificate status information that would be accepted as legitimate, undermining the entire certificate revocation checking system.
From a cybersecurity perspective this vulnerability aligns with common attack patterns documented in the attack tree framework where certificate validation bypasses represent a preferred method for attackers to compromise secure communications. The weakness manifests as a failure to properly validate the ocsp response binding, which can be categorized under security controls failures that have been previously documented in industry standards and best practices.
Organizations should immediately upgrade to the patched versions of Bouncy Castle for Java including 1.85 for standard releases, 2.73.12 for LTS versions, and the appropriate fips compliant releases to address this issue. The mitigation strategy involves not only updating the cryptographic libraries but also implementing additional monitoring to detect potential exploitation attempts and ensuring that certificate validation processes are properly configured to enforce proper ocsp response binding verification.
The vulnerability demonstrates the critical importance of proper certificate validation implementation and highlights how seemingly minor flaws in cryptographic library implementations can have far-reaching consequences for security infrastructure. This issue serves as a reminder of the necessity for comprehensive testing of cryptographic components and adherence to established security standards throughout the software development lifecycle.