High7.4Red Hat Linux

High [CVE-2026-58062] Bouncy Castle for Java: Certificate validation bypass via stapled OCSP response

This high-severity Red Hat Linux advisory covers CVE-2026-58062 affecting Red Hat AMQ Clients, Red Hat Ceph Storage 9, Red Hat Enterprise Linux 8.

CVE-2026-58062 Published Aug 3, 2026Updated by vendor Aug 3, 2026

CVE-2026-58062

Affected products & platforms

Red Hat LinuxRed Hat Enterprise Linux

Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Get CVE alerts See app features

Summary

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

This vulnerability allows a remote attacker to bypass certificate validation by presenting a manipulated Online Certificate Status Protocol (OCSP) response.

The system would accept this invalid response without properly verifying its binding to the checked certificate, which could lead to a failure in authenticating digital certificates and potentially result in information disclosure or other security compromises. Red Hat severity: Important — CVSS 7.4 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N).

Weakness: CWE-295. Affected Red Hat products: Red Hat AMQ Clients; Red Hat Ceph Storage 9; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; Red Hat JBoss Enterprise Application Platform 7; Red Hat Single Sign-On 7.

Red Hat does not currently list a fixing RHSA for this CVE.

Affected products named by the advisory: Red Hat package: resteasy.

Affected versions

< 1.85
< 2.73.12
< 2.0.2
< 2.0.X
< 2.1.3
< 2.1.X

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.