Improper Verification of Cryptographic Signature Affecting org.bouncycastle:bcpg-debug-jdk18on package, versions [1.81,1.85)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JAVA-ORGBOUNCYCASTLE-18512832
- published4 Aug 2026
- disclosed3 Aug 2026
- creditUnknown
Introduced: 3 Aug 2026
NewCVE-2026-59643 (opens in a new tab)How to fix?
Upgrade org.bouncycastle:bcpg-debug-jdk18on to version 1.85 or higher.
Overview
Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature in the OnePassSignatures.verify() method of OpenPGPMessageInputStream, whose catch (PGPSignatureException) block for the dataSignature.sanitize(key, policy) check contains only a // continue comment and no actual continue statement, so execution falls through to cryptographic verification. An attacker who can obtain or collision-forge a trusted-key signature that uses a policy-rejected hash such as MD5, SHA-1, or RIPEMD160 can have it reported as valid through the isTestedCorrect() and getSignatures() API, since the policy rejection is discarded once the signature verifies cryptographically. This requires the application to rely on OpenPGP one-pass inline signature verification with a policy configured to reject those algorithms, keys, or subpackets, and the signature must still verify against a trusted key.