CVE-2025-14813

CVE-2025-14813 is a critical-severity security vulnerability in org.bouncycastle:bcprov-jdk14 (maven), affecting versions >= 1.59, <= 1.80.1. It is fixed in 1.80.2, 1.81.1, 1.84.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Bouncy Castle for Java GOST 28147 CTR mode reuses keystream after 255 blocks

The GOST 28147-2015 CTR mode implementation (G3413CTRBlockCipher) in the Legion of the Bouncy Castle BC-JAVA bcprov core module only increments the final byte of the counter, so the counter wraps after 255 blocks and the keystream is reused. Reusing CTR keystream allows an attacker who can observe two ciphertexts produced with the same key/IV to recover the XOR of the plaintexts, breaking confidentiality. Affects BC-JAVA from 1.59 before 1.84 (with backported fixes in 1.80.2 and 1.81.1).

Impact

Affected versions

org.bouncycastle:bcprov-jdk14 (>= 1.59, <= 1.80.1) org.bouncycastle:bcprov-jdk15to18 (>= 1.59, <= 1.80.1) org.bouncycastle:bcprov-jdk18on (>= 1.59, <= 1.80.1) org.bouncycastle:bcprov-debug-jdk14 (>= 1.59, <= 1.80.1) org.bouncycastle:bcprov-debug-jdk15to18 (>= 1.59, <= 1.80.1) org.bouncycastle:bcprov-debug-jdk18on (>= 1.59, <= 1.80.1) org.bouncycastle:bcprov-ext-jdk14 (>= 1.59, <= 1.78.1) org.bouncycastle:bcprov-ext-jdk15to18 (>= 1.59, <= 1.78.1) org.bouncycastle:bcprov-ext-jdk18on (>= 1.59, <= 1.78.1) org.bouncycastle:bcprov-ext-debug-jdk14 (>= 1.59, <= 1.74) org.bouncycastle:bcprov-ext-debug-jdk15to18 (>= 1.59, <= 1.77) org.bouncycastle:bcprov-ext-debug-jdk18on (>= 1.59, <= 1.77) org.bouncycastle:bcprov-jdk14 (= 1.81.0) org.bouncycastle:bcprov-jdk15to18 (= 1.81.0) org.bouncycastle:bcprov-jdk18on (= 1.81.0) org.bouncycastle:bcprov-debug-jdk14 (= 1.81.0) org.bouncycastle:bcprov-debug-jdk15to18 (= 1.81.0) org.bouncycastle:bcprov-debug-jdk18on (= 1.81.0) org.bouncycastle:bcprov-jdk14 (>= 1.82, <= 1.83) org.bouncycastle:bcprov-jdk15to18 (>= 1.82, <= 1.83) org.bouncycastle:bcprov-jdk18on (>= 1.82, <= 1.83) org.bouncycastle:bcprov-debug-jdk14 (>= 1.82, <= 1.83) org.bouncycastle:bcprov-debug-jdk15to18 (>= 1.82, <= 1.83) org.bouncycastle:bcprov-debug-jdk18on (>= 1.82, <= 1.83)

Security releases

org.bouncycastle:bcprov-jdk18on → 1.80.2 (maven) org.bouncycastle:bcprov-jdk18on → 1.81.1 (maven) org.bouncycastle:bcprov-jdk14 → 1.84 (maven) org.bouncycastle:bcprov-jdk15to18 → 1.84 (maven) org.bouncycastle:bcprov-jdk18on → 1.84 (maven) org.bouncycastle:bcprov-debug-jdk14 → 1.84 (maven) org.bouncycastle:bcprov-debug-jdk15to18 → 1.84 (maven) org.bouncycastle:bcprov-debug-jdk18on → 1.84 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.bouncycastle:bcprov-jdk18on to 1.80.2 or later; org.bouncycastle:bcprov-jdk18on to 1.81.1 or later; org.bouncycastle:bcprov-jdk14 to 1.84 or later; org.bouncycastle:bcprov-jdk15to18 to 1.84 or later; org.bouncycastle:bcprov-jdk18on to 1.84 or later; org.bouncycastle:bcprov-debug-jdk14 to 1.84 or later; org.bouncycastle:bcprov-debug-jdk15to18 to 1.84 or later; org.bouncycastle:bcprov-debug-jdk18on to 1.84 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2025-14813? CVE-2025-14813 is a critical-severity security vulnerability in org.bouncycastle:bcprov-jdk14 (maven), affecting versions >= 1.59, <= 1.80.1. It is fixed in 1.80.2, 1.81.1, 1.84.
  2. Which packages are affected by CVE-2025-14813?
    • org.bouncycastle:bcprov-jdk14 (maven) (versions >= 1.59, <= 1.80.1)
    • org.bouncycastle:bcprov-jdk15to18 (maven) (versions >= 1.59, <= 1.80.1)
    • org.bouncycastle:bcprov-jdk18on (maven) (versions >= 1.59, <= 1.80.1)
    • org.bouncycastle:bcprov-debug-jdk14 (maven) (versions >= 1.59, <= 1.80.1)
    • org.bouncycastle:bcprov-debug-jdk15to18 (maven) (versions >= 1.59, <= 1.80.1)
    • org.bouncycastle:bcprov-debug-jdk18on (maven) (versions >= 1.59, <= 1.80.1)
    • org.bouncycastle:bcprov-ext-jdk14 (maven) (versions >= 1.59, <= 1.78.1)
    • org.bouncycastle:bcprov-ext-jdk15to18 (maven) (versions >= 1.59, <= 1.78.1)
    • org.bouncycastle:bcprov-ext-jdk18on (maven) (versions >= 1.59, <= 1.78.1)
    • org.bouncycastle:bcprov-ext-debug-jdk14 (maven) (versions >= 1.59, <= 1.74)
    • org.bouncycastle:bcprov-ext-debug-jdk15to18 (maven) (versions >= 1.59, <= 1.77)
    • org.bouncycastle:bcprov-ext-debug-jdk18on (maven) (versions >= 1.59, <= 1.77)
  3. Is there a fix for CVE-2025-14813? Yes. CVE-2025-14813 is fixed in 1.80.2, 1.81.1, 1.84. Upgrade to this version or later.
  4. Is CVE-2025-14813 exploitable, and should I be worried? Whether CVE-2025-14813 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2025-14813 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2025-14813?
    • Upgrade org.bouncycastle:bcprov-jdk18on to 1.80.2 or later
    • Upgrade org.bouncycastle:bcprov-jdk18on to 1.81.1 or later
    • Upgrade org.bouncycastle:bcprov-jdk14 to 1.84 or later
    • Upgrade org.bouncycastle:bcprov-jdk15to18 to 1.84 or later
    • Upgrade org.bouncycastle:bcprov-jdk18on to 1.84 or later
    • Upgrade org.bouncycastle:bcprov-debug-jdk14 to 1.84 or later
    • Upgrade org.bouncycastle:bcprov-debug-jdk15to18 to 1.84 or later
    • Upgrade org.bouncycastle:bcprov-debug-jdk18on to 1.84 or later

Other vulnerabilities in org.bouncycastle:bcprov-jdk14

CVE-IDSeverityPackage summary
CVE-2026-5598Highorg.bouncycastle:bcprov-jdk15to18: Bouncy Castle Has Covert Timing Channel VulnerabilityCVE-2026-0636Mediumorg.bouncycastle:bcprov-jdk14: Bouncy Castle has an LDAP injectionCVE-2025-8885Mediumorg.bouncycastle:bcprov-jdk14: Bouncy Castle for Java on All (API modules) allows Excessive AllocationCVE-2024-30171Mediumorg.bouncycastle:bctls-fips: Bouncy Castle affected by timing side-channel for RSA key exchange ("The Marvin Attack")CVE-2024-30172MediumBouncyCastle: Bouncy Castle crafted signature and public key can be used to trigger an infinite loop

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo