Improper Verification of Cryptographic Signature Affecting org.bouncycastle:bcpkix-fips package, versions [,1.0.12)[2.0.7,2.0.12)[2.1.8,2.1.12)
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-18513029
- published4 Aug 2026
- disclosed3 Aug 2026
- creditUnknown
Introduced: 3 Aug 2026
NewCVE-2026-59639 (opens in a new tab)How to fix?
Upgrade org.bouncycastle:bcpkix-fips to version 1.0.12, 2.0.12, 2.1.12 or higher.
Overview
Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature in the CMSSignedData.verifySignatures(SignerInformationVerifierProvider, boolean) method, which iterates the signer set and returns true on loop completion without checking that any signer is present. An attacker can have completely unsigned content accepted as authentic by submitting a degenerate CMS or PKCS#7 SignedData that carries arbitrary content with an empty signerInfos set, which RFC 5652 permits. This affects applications that treat the true return value as proof of authenticity without separately asserting that an expected signer is present.