Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-58062: In Bouncy Castle for Java before 1.85, Stapled OCSP response accepted without binding to the checked certifica

44
This month
CRITICAL 9.1REMOTEUPGRADEUPGRADEUPGRADE

CVE-2026-58062 is a critical-severity flaw (CVSS 9.1) affecting bc-java, bouncy castle for java lts, fips java api. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

  • Critical severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.1 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.4% (top 70%)
CISA exploited listNo
WeaknessCWE-295
Published2026-08-03
Last modified2026-09-02
Publisher (CNA): bcorg · Vendor: bouncycastle

Share: LinkedIn · X · Reddit

Last updated 2026-09-02 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

bouncycastle bc-java UPGRADE
Affected: >= 1.66 and < 1.85
Fixed in: 1.85
Safe to downgrade to: a release before 1.66
1. Check installed version
apt-cache policy bc-java || rpm -q bc-java || bc-java --version
2. UPGRADE to 1.85 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade bc-java
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade bc-java
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.66 (Debian / Ubuntu)
apt-cache madison bc-java sudo apt install bc-java=<VERSION_BEFORE_1.66> sudo apt-mark hold bc-java
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list bc-java sudo dnf downgrade bc-java-<VERSION_BEFORE_1.66> sudo dnf versionlock add bc-java
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
bouncycastle bouncy castle for java lts UPGRADE
Affected: <= 2.73.11
Fixed in: newer than 2.73.11
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy bouncy-castle-for-java-lts || rpm -q bouncy-castle-for-java-lts || bouncy-castle-for-java-lts --version
2. UPGRADE to newer than 2.73.11 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade bouncy-castle-for-java-lts
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade bouncy-castle-for-java-lts
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
bouncycastle fips java api UPGRADE
Affected: < 2.0.2 · >= 2.1.0 and < 2.1.3
Fixed in: 2.0.2, 2.1.3
Safe to downgrade to: a release before 2.1.0
1. Check installed version
apt-cache policy fips-java-api || rpm -q fips-java-api || fips-java-api --version
2. UPGRADE to 2.0.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade fips-java-api
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade fips-java-api
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.1.0 (Debian / Ubuntu)
apt-cache madison fips-java-api sudo apt install fips-java-api=<VERSION_BEFORE_2.1.0> sudo apt-mark hold fips-java-api
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list fips-java-api sudo dnf downgrade fips-java-api-<VERSION_BEFORE_2.1.0> sudo dnf versionlock add fips-java-api
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-58062?

bc-java: upgrade to 1.85; bouncy castle for java lts: upgrade to newer than 2.73.11; fips java api: upgrade to 2.0.2, 2.1.3. Exact commands for each OS are on this page.

Is CVE-2026-58062 being exploited?

CVE-2026-58062 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-58062 affect?

CVE-2026-58062 affects bc-java, bouncy castle for java lts, fips java api. Severity is critical (CVSS 9.1). 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

How urgent is CVE-2026-58062?

Priority 44/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

Java vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.