Skip to main content
← Maven

org.bouncycastle:bcprov-jdk14

26 known vulnerabilities (1 critical, 4 high, 3 medium), with the versions each affects and the releases that fix them.

Latest release
1.86 (Sep 11, 2026): no advisory affects it
Newest unaffected release
1.86 (Sep 11, 2026), the latest release
Advisories
26 · 1 critical, 4 high, 3 medium
Dependents
6
Releases
46 since 1.38 (Jul 9, 2009)
Registry
Maven Central
Releases read
Nov 8, 2026

Version timeline

Show all 26 advisoriesShow fewer advisories
Every release cve.now has on record, lowest version on the left; each bar is a run of versions an advisory affects.

Advisories 26

  • Non-constant time comparisons risk private key leakage in FrodoKEM.

    Affected: from 1.71, fixed in 1.84.

    Fixed in 1.84 (released Apr 15, 2026, the day of disclosure).

    The latest release, 1.86, is not affected.

  • CVE-2026-0636Medium 5.5

    LDAP Injection Vulnerability in LDAPStoreHelper.java

    Affected: from 1.74, fixed in 1.84.

    Fixed in 1.84 (released Apr 15, 2026, the day of disclosure).

    The latest release, 1.86, is not affected.

  • CVE-2025-14813Critical 9.3

    GOSTCTR implementation unable to process more than 255 blocks correctly

    Affected: from 1.59, through 1.80.1; versions 1.81.0; from 1.82, fixed in 1.84.

    Fixed in 1.84 (released Apr 15, 2026, the day of disclosure).

    The latest release, 1.86, is not affected.

  • CVE-2025-8885Medium 6.3

    Possible DOS in processing specially formed ASN.1 Object Identifiers

    Affected: from 1.0, fixed in 1.78.

    Fixed in 1.78 (released Apr 6, 2024, 493 days before disclosure).

    The latest release, 1.86, is not affected.

  • An issue was discovered in ECCurve.java and ECCurve.cs in Bouncy Castle Java (BC Java) before 1.78, BC Java LTS before 2.73.6, BC-FJA…

    Affected: fixed in 1.78.

    Fixed in 1.78 (released Apr 6, 2024, 33 days before disclosure).

    The latest release, 1.86, is not affected.

  • An issue was discovered in Bouncy Castle Java Cryptography APIs before 1.78.

    Affected: from 1.73, fixed in 1.78.

    Fixed in 1.78 (released Apr 6, 2024, 33 days before disclosure).

    The latest release, 1.86, is not affected.

  • CVE-2024-30171Medium 5.9

    An issue was discovered in Bouncy Castle Java TLS API and JSSE Provider before 1.78.

    Affected: fixed in 1.78.

    Fixed in 1.78 (released Apr 6, 2024, 33 days before disclosure).

    The latest release, 1.86, is not affected.

  • An issue was discovered in the Bouncy Castle Crypto Package For Java before BC TLS Java 1.0.19 (ships with BC Java 1.78, BC Java (LTS)…

    Affected: from 1.61, fixed in 1.78.

    Fixed in 1.78 (released Apr 6, 2024, 27 days before disclosure).

    The latest release, 1.86, is not affected.

  • Bouncy Castle for Java before 1.73 contains a potential Denial of Service (DoS) issue within the Bouncy Castle…

    Affected: fixed in 1.73.

    Fixed in 1.73 (released Apr 12, 2023, 225 days before disclosure).

    The latest release, 1.86, is not affected.

  • Bouncy Castle For Java before 1.74 is affected by an LDAP injection vulnerability.

    Affected: from 1.49, fixed in 1.74.

    Fixed in 1.74 (released Jun 16, 2023, 19 days before disclosure).

    The latest release, 1.86, is not affected.

  • Bouncy Castle BC Java before 1.66, BC C# .NET before 1.8.7, BC-FJA before 1.0.1.2, 1.0.2.1, and BC-FNA before 1.0.1.1 have a timing issue…

    Affected: fixed in 1.66.

    Fixed in 1.67 (released Nov 1, 2020, 200 days before disclosure, the advisory names 1.66, which was never published).

    The latest release, 1.86, is not affected.

  • An issue was discovered in Legion of the Bouncy Castle BC Java 1.65 and 1.66.

    Affected: from 1.65, fixed in 1.67.

    Fixed in 1.67 (released Nov 1, 2020, 47 days before disclosure).

    The latest release, 1.86, is not affected.

  • In Legion of the Bouncy Castle BC before 1.61 and BC-FJA before 1.0.1.2, attackers can obtain sensitive information about a private…

    Affected: fixed in 1.61.

    Fixed in 1.61 (released Feb 15, 2019, 626 days before disclosure).

    The latest release, 1.86, is not affected.

  • The ASN.1 parser in Bouncy Castle Crypto (aka BC Java) 1.63 can trigger a large attempted memory allocation, and resultant…

    Affected: from 1.63, fixed in 1.64.

    Fixed in 1.64 (released Oct 12, 2019, 4 days after disclosure).

    The latest release, 1.86, is not affected.

  • 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…

    Affected: fixed in 1.60.

    Fixed in 1.60 (released Jul 6, 2018, 31 days after disclosure).

    The latest release, 1.86, is not affected.

Show all 26 advisoriesShow fewer advisories
  • In the Bouncy Castle JCE Provider version 1.55 and earlier the ECIES implementation allowed the use of ECB mode.

    Affected: fixed in 1.56.

    Fixed in 1.56 (released May 12, 2017, 388 days before disclosure).

    The latest release, 1.86, is not affected.

  • In the Bouncy Castle JCE Provider version 1.55 and earlier the other party DH public key is not fully validated.

    Affected: fixed in 1.56.

    Fixed in 1.56 (released May 12, 2017, 388 days before disclosure).

    The latest release, 1.86, is not affected.

  • In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES/ECIES CBC mode vulnerable to padding oracle attack.

    Affected: fixed in 1.56.

    Fixed in 1.56 (released May 12, 2017, 388 days before disclosure).

    The latest release, 1.86, is not affected.

  • In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES implementation allowed the use of ECB mode.

    Affected: fixed in 1.56.

    Fixed in 1.56 (released May 12, 2017, 388 days before disclosure).

    The latest release, 1.86, is not affected.

  • 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…

    Affected: fixed in 1.56.

    Fixed in 1.56 (released May 12, 2017, 388 days before disclosure).

    The latest release, 1.86, is not affected.

  • In the Bouncy Castle JCE Provider version 1.55 and earlier ECDSA does not fully validate ASN.1 encoding of signature on verification.

    Affected: fixed in 1.56.

    Fixed in 1.56 (released May 12, 2017, 388 days before disclosure).

    The latest release, 1.86, is not affected.

  • In the Bouncy Castle JCE Provider version 1.55 and earlier DSA signature generation is vulnerable to timing attack.

    Affected: fixed in 1.56.

    Fixed in 1.56 (released May 12, 2017, 388 days before disclosure).

    The latest release, 1.86, is not affected.

  • In the Bouncy Castle JCE Provider versions 1.51 to 1.55, a carry propagation bug was introduced in the implementation of squaring for…

    Affected: from 1.51, fixed in 1.56.

    Fixed in 1.56 (released May 12, 2017, 388 days before disclosure).

    The latest release, 1.86, is not affected.

  • In the Bouncy Castle JCE Provider version 1.55 and earlier the primary engine class used for AES was AESFastEngine.

    Affected: fixed in 1.56.

    Fixed in 1.56 (released May 12, 2017, 388 days before disclosure).

    The latest release, 1.86, is not affected.

  • In Bouncy Castle JCE Provider version 1.55 and earlier the DSA does not fully validate ASN.1 encoding of signature on verification.

    Affected: from 1.38, fixed in 1.56.

    Fixed in 1.56 (released May 12, 2017, 385 days before disclosure).

    The latest release, 1.86, is not affected.

  • The Bouncy Castle Java library before 1.51 does not validate a point is withing the elliptic curve, which makes it easier for remote…

    Affected: fixed in 1.51.

    Fixed in 1.51 (released Jul 28, 2014, 469 days before disclosure).

    The latest release, 1.86, is not affected.