CVE-2026-59639: CMS verifySignatures returns true for SignedData with zero signers

August 3, 2026 (updated September 16, 2026)

Affects Bouncy Castle for Java before 1.85. CMSSignedData.verifySignatures() iterates the signer set and returns true once the loop completes, without requiring that any signer be present. RFC 5652 allows a degenerate SignedData with an empty signerInfos set, and neither the ASN.1 layer nor SignerInformationStore rejects one. An attacker can submit a CMS or PKCS#7 blob carrying arbitrary content and no signers; applications treating the return value as proof of authenticity will accept unsigned content.

References

github.com/bcgit/bc-java/commit/99ddc6dcc6782e6a76b0dd587c77e62eb7096ad0
github.com/bcgit/bc-java/wiki/CVE-2026-59639
nvd.nist.gov/vuln/detail/CVE-2026-59639

Code Behaviors & Features

Detect and mitigate CVE-2026-59639 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →