This vulnerability (CVE-2026-5598) in BC-JAVA is a covert timing channel caused by non-constant time comparisons in the FrodoKEM cryptographic implementation. It allows an unauthenticated remote attacker to send malformed ciphertexts that trigger timing variations during private key verification. By analyzing these timing differences statistically over many requests, the attacker may extract private key information. The issue affects BC-JAVA versions from 1.71 before 1.80.2, from 1.81 before 1.81.1, and from 1.82 before 1.84. Red Hat advisory confirms the vulnerability and provides a fix by upgrading Bouncy Castle to version 1.84. The advisory also recommends mitigation via rate limiting and anomaly detection on cryptographic handshake failures. No known exploits in the wild have been reported.

The primary impact is the potential leakage of private keys used in the FrodoKEM implementation, which can compromise encrypted communications or authentication mechanisms relying on these keys. The vulnerability requires no privileges or user interaction but demands a high volume of crafted requests for statistical timing analysis. This can lead to unauthorized access to sensitive cryptographic material, posing a high confidentiality risk. Integrity and availability are not impacted.

A security update is available that fixes this vulnerability by upgrading BC-JAVA to version 1.84 or later. Users should apply this official patch promptly. Additionally, implement aggressive rate limiting and anomaly detection to identify and block unusual high-frequency cryptographic handshake failures or anomalous traffic patterns targeting key exchange endpoints. These mitigations reduce the risk of exploitation while patching is applied.