Bouncycastle is a widely embedded cryptographic library that provides Java-based encryption, digital signature, and certificate-handling functionality across a large ecosystem of downstream applications and frameworks, despite a narrow direct product portfolio. Its prominence in the landscape stems from deep supply-chain integration rather than direct end-user deployment, making vulnerabilities in the library's core components—particularly BC-Java and its FIPS variant—capable of affecting a much broader population of dependent products. The recurring weakness classes center on cryptographic verification and implementation issues, including improper signature verification, exposure of sensitive cryptographic material, observable timing discrepancies, and reliance on broken or risky algorithms, reflecting the complexity and precision demands of cryptographic code. Defenders should track Bouncycastle releases closely and prioritize inventory of downstream products that embed it, since remediation typically cascades through application rebuilds rather than isolated library patching; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Bouncycastle over time
Signals from CVEs in this vendor scope (25 CVEs).
25 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2017-13098MEDIUM BouncyCastle TLS prior to version 1.0.3, when configured to use the JCE (Java Cryptography Extension) for cryptographic functions, provides a weak Bleichenbacher oracle when any TL | Dec 13, 2017 | 5.9 | 39 | NO | YES |
CVE-2018-1000613CRITICAL Legion of the Bouncy Castle Legion of the Bouncy Castle Java Cryptography APIs 1.58 up to but not including 1.60 contains a CWE-470: Use of Externally-Controlled Input to Select Cl | Jul 9, 2018 | 9.8 | 32 | NO | NO |
CVE-2020-28052HIGH An issue was discovered in Legion of the Bouncy Castle BC Java 1.65 and 1.66. The OpenBSDBCrypt.checkPassword utility method compared incorrect data when checking the password, all | Dec 18, 2020 | 8.1 | 30 | NO | NO |
CVE-2019-17359HIGH The ASN.1 parser in Bouncy Castle Crypto (aka BC Java) 1.63 can trigger a large attempted memory allocation, and resultant OutOfMemoryError error, via crafted ASN.1 data. This is f | Oct 8, 2019 | 7.5 | 29 | NO | NO |
CVE-2018-1000180HIGH Bouncy Castle BC 1.54 - 1.59, BC-FJA 1.0.0, BC-FJA 1.0.1 and earlier have a flaw in the Low-level interface to RSA key pair generator, specifically RSA Key Pairs generated in low-l | Jun 5, 2018 | 7.5 | 26 | NO | NO |
CVE-2007-6721HIGH The Legion of the Bouncy Castle Java Cryptography API before release 1.38, as used in Crypto Provider Package before 1.36, has unknown impact and remote attack vectors related to " | Mar 30, 2009 | 10.0 | 26 | NO | NO |
CVE-2016-1000344HIGH In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES implementation allowed the use of ECB mode. This mode is regarded as unsafe and support for it has been removed | Jun 4, 2018 | 7.4 | 25 | NO | NO |
CVE-2016-1000343HIGH In the Bouncy Castle JCE Provider version 1.55 and earlier the DSA key pair generator generates a weak private key if used with default values. If the JCA key pair generator is not | Jun 4, 2018 | 7.5 | 25 | NO | NO |
CVE-2016-1000352HIGH In the Bouncy Castle JCE Provider version 1.55 and earlier the ECIES implementation allowed the use of ECB mode. This mode is regarded as unsafe and support for it has been removed | Jun 4, 2018 | 7.4 | 24 | NO | NO |
CVE-2016-1000342HIGH In the Bouncy Castle JCE Provider version 1.55 and earlier ECDSA does not fully validate ASN.1 encoding of signature on verification. It is possible to inject extra elements in the | Jun 4, 2018 | 7.5 | 24 | NO | NO |
Signals from CVEs in this vendor scope (25 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Bouncycastle.
Media articles that mention a CVE ID that affects a product developed by Bouncycastle — matched by CVE ID, not by vendor name.