# CVE-2026-58062: Stapled OCSP response accepted without binding to the checked certificate

> Attackers can bypass certificate validation by presenting a stapled OCSP response not bound to the checked certificate in Bouncy Castle Java libraries.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** CLEANSTART-2026-IC52490, CLEANSTART-2026-NV23074, CLEANSTART-2026-QI70925, CLEANSTART-2026-QK17801, CLEANSTART-2026-VS62795, DEBIAN-CVE-2026-58062, GHSA-j295-77c3-9frf, UBUNTU-CVE-2026-58062

## What is CVE-2026-58062?

CVE-2026-58062 is a critical vulnerability in Bouncycastle Bc-Java, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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).

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-58062?

It affects 3 products.


Products: Bouncycastle Bc-Java, Bouncycastle Bouncy Castle for Java Lts, Bouncycastle Fips Java Api.

## How do I fix CVE-2026-58062?

Upgrade to a fixed version.

## Is CVE-2026-58062 being exploited?

There is no known exploitation of CVE-2026-58062 in the wild and no public exploit code.

Public exploit code:

- Offline scanner telling you which of the 2026 Bouncy Castle CVEs actually apply to you - across BC, BC-LTS and BC-FJA (FIPS), which do not share a version scheme. CVE-2026-58062 / CVE-2026-8763 / CVE-2026-59650 / CVE-2026-59638 (github_poc): https://github.com/xiaoqiMikko/bc-check

## Other vulnerabilities in Bouncycastle Bc-Java

- [CVE-2007-6721](https://insights.sbomify.com/CVE-2007-6721/): Legion of the Bouncy Castle Java Cryptography API Bleichenbacher Oracle Vulnerability (critical 10.0)
- [CVE-2018-1000613](https://insights.sbomify.com/CVE-2018-1000613/): Deserialization of Untrusted Data in Bouncy castle (critical 9.8)
- [CVE-2026-59638](https://insights.sbomify.com/CVE-2026-59638/): JSSE hostname verifier CN-fallback enabled by default despite documented opt-in (critical 9.3)
- [CVE-2026-59650](https://insights.sbomify.com/CVE-2026-59650/): MTI/A0 DH agreement exponentiates unvalidated peer value (critical 9.3)
- [CVE-2026-8763](https://insights.sbomify.com/CVE-2026-8763/): Name Constraints bypass via trailing dot in rfc822Name and URI (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-58062 and fix it if it is affected.

What it is: CVE-2026-58062 is a critical vulnerability in Bouncycastle Bc-Java, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-58062 in the wild and no public exploit code.

Affected product: Bouncycastle Bc-Java. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-58062/ (Markdown: https://insights.sbomify.com/CVE-2026-58062/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-58062
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-58062
- OSV: https://osv.dev/vulnerability/CVE-2026-58062

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-58062/
Summaries are generated and may contain mistakes; the official description above is the record.