# CVE-2025-14813: GOSTCTR implementation unable to process more than 255 blocks correctly > The GOSTCTR implementation fails to process more than 255 blocks correctly, potentially compromising data integrity or confidentiality in cryptographic operations. - **Severity:** Critical 9.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/RE:M/U:Red`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Apr 2026 - **Updated:** 18 Sep 2026 - **Also known as:** CLEANSTART-2026-KG24166, CLEANSTART-2026-VY85613, CLSA-2026-1784769552, CLSA-2026-1785117186, CLSA-2026-1788269927, ECHO-9557-b365-5d38, GHSA-574f-3g2m-x479, MINI-2384-q93f-336w, MINI-2p64-rc8m-c38j, MINI-34wj-wjj6-783m, MINI-385p-gg2v-3gwg, MINI-38v6-8wfg-66qg, MINI-4242-wj82-9cg4, MINI-4gv3-m865-cgv3, MINI-4hjf-p7pv-qjcq, MINI-4v2h-wh77-4x8w, MINI-4vgw-7g3r-7xp6, MINI-4wwg-rr84-r32f, MINI-5629-r4qq-w45r, MINI-5prg-r73c-995r, MINI-78hq-8hgm-mhv8, MINI-7p5w-f8p8-rwxm, MINI-7xf2-vpf4-cwrj, MINI-8fr5-cvqx-x2g6, MINI-8gr6-prfj-8c5r, MINI-8q54-5v7h-frr6, MINI-8qg3-fm7j-9jgh, MINI-9mvh-827v-vqhp, MINI-9q7x-2v26-fprr, MINI-cc8f-36r3-9wrp, MINI-cp6c-64vf-4v9g, MINI-cx6c-hw53-7jcx, MINI-fm7v-h8cj-7pp5, MINI-g8rc-25cv-rv3g, MINI-gg36-wvfg-x5w7, MINI-gwr4-278v-375m, MINI-hph9-qx49-gqhc, MINI-j4pq-f9cx-pqxf, MINI-j647-c9rx-gghg, MINI-jmwx-7rr5-4jcv, MINI-jr2q-969w-jh75, MINI-jw8w-mjxh-r3fj, MINI-m5x8-jjgr-x792, MINI-m89f-crf3-5v72, MINI-mjff-m3wc-vr4r, MINI-mv79-3h6g-j8qw, MINI-p9rw-2c58-2746, MINI-q5q3-367v-cccr, MINI-qcpf-g5h4-46r6, MINI-qx5c-2rmw-h65p, MINI-rjr9-jjpm-82gx, MINI-rqm7-wrx6-975g, MINI-rr7h-g5pr-f2g6, MINI-rw2j-g3h4-9vwq, MINI-v7vw-wc97-f2pf, MINI-v968-mw6p-mcfh, MINI-w2g3-g2p5-qj6v, MINI-w89c-f2vp-rjch, MINI-wq97-p985-ph24, MINI-xqhg-h4m4-3xcp, MINI-xrwr-px6r-v53c, ROOT-APP-MAVEN-CVE-2025-14813, UBUNTU-CVE-2025-14813 ## What is CVE-2025-14813? CVE-2025-14813 is a critical vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA, published on 15 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description : Use of a Broken or Risky Cryptographic Algorithm vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA bcprov on all (core modules). This vulnerability is associated with program files G3413CTRBlockCipher. This issue affects BC-JAVA: from 1.59 before 1.80.2, from 1.81 before 1.81.1, from 1.82 before 1.84. Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) ## Which versions are affected by CVE-2025-14813? 40 open source packages ship an affected version, including org.bouncycastle:bcprov-debug-jdk14, org.bouncycastle:bcprov-debug-jdk15on and org.bouncycastle:bcprov-debug-jdk15to18. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.bouncycastle:bcprov-debug-jdk14` | Maven | All versions | None | | `org.bouncycastle:bcprov-debug-jdk14` | Maven | All versions | None | | `org.bouncycastle:bcprov-debug-jdk14` | Maven | From 1.59 to 1.80.1 | None | | `org.bouncycastle:bcprov-debug-jdk14` | Maven | From 1.59 to 1.80.1 | None | | `org.bouncycastle:bcprov-debug-jdk14` | Maven | From 1.82 | 1.84 | | `org.bouncycastle:bcprov-debug-jdk14` | Maven | From 1.82 | 1.84 | | `org.bouncycastle:bcprov-debug-jdk15on` | Maven | All versions to 1.7.0 | None | | `org.bouncycastle:bcprov-debug-jdk15on` | Maven | All versions to 1.7.0 | None | | `org.bouncycastle:bcprov-debug-jdk15to18` | Maven | All versions | None | | `org.bouncycastle:bcprov-debug-jdk15to18` | Maven | All versions | None | | `org.bouncycastle:bcprov-debug-jdk15to18` | Maven | From 1.59 to 1.80.1 | None | | `org.bouncycastle:bcprov-debug-jdk15to18` | Maven | From 1.59 to 1.80.1 | None | | `org.bouncycastle:bcprov-debug-jdk15to18` | Maven | From 1.82 | 1.84 | | `org.bouncycastle:bcprov-debug-jdk15to18` | Maven | From 1.82 | 1.84 | | `org.bouncycastle:bcprov-debug-jdk18on` | Maven | All versions | None | | `org.bouncycastle:bcprov-debug-jdk18on` | Maven | All versions | None | | `org.bouncycastle:bcprov-debug-jdk18on` | Maven | From 1.59 to 1.80.1 | None | | `org.bouncycastle:bcprov-debug-jdk18on` | Maven | From 1.59 to 1.80.1 | None | | `org.bouncycastle:bcprov-debug-jdk18on` | Maven | From 1.82 | 1.84 | | `org.bouncycastle:bcprov-debug-jdk18on` | Maven | From 1.82 | 1.84 | | `org.bouncycastle:bcprov-ext-debug-jdk14` | Maven | From 1.59 to 1.74 | None | | `org.bouncycastle:bcprov-ext-debug-jdk14` | Maven | From 1.59 to 1.74 | None | | `org.bouncycastle:bcprov-ext-debug-jdk15to18` | Maven | From 1.59 to 1.77 | None | | `org.bouncycastle:bcprov-ext-debug-jdk15to18` | Maven | From 1.59 to 1.77 | None | | `org.bouncycastle:bcprov-ext-debug-jdk18on` | Maven | From 1.59 to 1.77 | None | | `org.bouncycastle:bcprov-ext-debug-jdk18on` | Maven | From 1.59 to 1.77 | None | | `org.bouncycastle:bcprov-ext-jdk14` | Maven | From 1.59 to 1.78.1 | None | | `org.bouncycastle:bcprov-ext-jdk14` | Maven | From 1.59 to 1.78.1 | None | | `org.bouncycastle:bcprov-ext-jdk15to18` | Maven | From 1.59 to 1.78.1 | None | | `org.bouncycastle:bcprov-ext-jdk15to18` | Maven | From 1.59 to 1.78.1 | None | | `org.bouncycastle:bcprov-ext-jdk18on` | Maven | From 1.59 to 1.78.1 | None | | `org.bouncycastle:bcprov-ext-jdk18on` | Maven | From 1.59 to 1.78.1 | None | | `org.bouncycastle:bcprov-jdk14` | Maven | All versions | None | | `org.bouncycastle:bcprov-jdk14` | Maven | All versions | None | | `org.bouncycastle:bcprov-jdk14` | Maven | From 1.59 to 1.80.1 | None | | `org.bouncycastle:bcprov-jdk14` | Maven | From 1.59 to 1.80.1 | None | | `org.bouncycastle:bcprov-jdk14` | Maven | From 1.82 | 1.84 | | `org.bouncycastle:bcprov-jdk14` | Maven | From 1.82 | 1.84 | | `org.bouncycastle:bcprov-jdk15on` | Maven | All versions to 1.7.0 | None | | `org.bouncycastle:bcprov-jdk15on` | Maven | All versions to 1.7.0 | None | ## How do I fix CVE-2025-14813? Upgrade org.bouncycastle:bcprov-debug-jdk14 to 1.84 or later. ## Is CVE-2025-14813 being exploited? There is no known exploitation of CVE-2025-14813 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-14813 and fix it if it is affected. What it is: CVE-2025-14813 is a critical vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA, published on 15 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-14813 in the wild and no public exploit code. Affected packages and fixed versions: - org.bouncycastle:bcprov-debug-jdk14 (Maven): affected all versions; no fix listed - org.bouncycastle:bcprov-debug-jdk14 (Maven): affected all versions; no fix listed - org.bouncycastle:bcprov-debug-jdk14 (Maven): affected from 1.59 up to 1.80.1; no fix listed - org.bouncycastle:bcprov-debug-jdk14 (Maven): affected from 1.59 up to 1.80.1; no fix listed - org.bouncycastle:bcprov-debug-jdk14 (Maven): affected from 1.82; fixed in 1.84 - org.bouncycastle:bcprov-debug-jdk14 (Maven): affected from 1.82; fixed in 1.84 - org.bouncycastle:bcprov-debug-jdk15on (Maven): affected all versions up to 1.7.0; no fix listed - org.bouncycastle:bcprov-debug-jdk15on (Maven): affected all versions up to 1.7.0; no fix listed - org.bouncycastle:bcprov-debug-jdk15to18 (Maven): affected all versions; no fix listed - org.bouncycastle:bcprov-debug-jdk15to18 (Maven): affected all versions; no fix listed - org.bouncycastle:bcprov-debug-jdk15to18 (Maven): affected from 1.59 up to 1.80.1; no fix listed - org.bouncycastle:bcprov-debug-jdk15to18 (Maven): affected from 1.59 up to 1.80.1; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-14813/ (Markdown: https://insights.sbomify.com/CVE-2025-14813/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14813 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14813 - OSV: https://osv.dev/vulnerability/CVE-2025-14813 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-14813/ Summaries are generated and may contain mistakes; the official description above is the record.