How severe is GHSA-574f-3g2m-x479?

GHSA-574f-3g2m-x479 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-574f-3g2m-x479?

GHSA-574f-3g2m-x479 affects the following packages: org.bouncycastle:bcprov-jdk14 (Maven), org.bouncycastle:bcprov-jdk15to18 (Maven), org.bouncycastle:bcprov-jdk18on (Maven), org.bouncycastle:bcprov-debug-jdk14 (Maven), org.bouncycastle:bcprov-debug-jdk15to18 (Maven), org.bouncycastle:bcprov-debug-jdk18on (Maven), org.bouncycastle:bcprov-ext-jdk14 (Maven), org.bouncycastle:bcprov-ext-jdk15to18 (Maven), and 18 more. Ecosystems affected: Maven.

How do I fix GHSA-574f-3g2m-x479?

A fix is available for GHSA-574f-3g2m-x479; check the affected-versions list above or the advisory for the patched release of org.bouncycastle:bcprov-jdk14, then make sure no transitive dependency still pins the vulnerable range.

How do I detect GHSA-574f-3g2m-x479 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.bouncycastle:bcprov-jdk14, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-574f-3g2m-x479 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-574f-3g2m-x479 actively exploited in the wild?

No public exploit code has been indexed for GHSA-574f-3g2m-x479 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-574f-3g2m-x479?

GHSA-574f-3g2m-x479 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 27th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-574f-3g2m-x479?

GHSA-574f-3g2m-x479 is classified as Broken Cryptographic Algorithm (CWE-327). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-574f-3g2m-x479 published, and has it been updated?

GHSA-574f-3g2m-x479 was published on April 17, 2026 and was last updated on September 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

Bouncy Castle for Java GOST 28147 CTR mode reuses keystream after 255 blocksGHSA-574f-3g2m-x479

HIGHFix: bcgit/bc-java@b425743

GHSA-574f-3g2m-x479 is a high-severity (CVSS 7.5) Broken Cryptographic Algorithm vulnerability in org.bouncycastle:bcprov-jdk14. A fix is available for org.bouncycastle:bcprov-jdk14 — see the affected versions and patch details below.

Also known asCVE-2025-14813

Published

Apr 17, 2026

Updated

Sep 24, 2026

Affected

26 pkgs

Patched

8 / 26

Exploits

None indexed

Exploitation data as of Nov 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-574f-3g2m-x479.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs27th percentile — riskier than 27% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

26 pkgs affected

☕org.bouncycastle:bcprov-jdk14☕org.bouncycastle:bcprov-jdk15to18☕org.bouncycastle:bcprov-jdk18on☕org.bouncycastle:bcprov-debug-jdk14☕org.bouncycastle:bcprov-debug-jdk15to18☕org.bouncycastle:bcprov-debug-jdk18on☕org.bouncycastle:bcprov-ext-jdk14☕org.bouncycastle:bcprov-ext-jdk15to18+18 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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).

Affected Packages

26 total 8 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.bouncycastle:bcprov-jdk14`	≥ 1.59	No fix
☕Maven	`org.bouncycastle:bcprov-jdk15to18`	≥ 1.59	No fix
☕Maven	`org.bouncycastle:bcprov-jdk18on`	≥ 1.59&&< 1.80.2	1.80.2`org.bouncycastle:bcprov-jdk18on:1.80.2`
☕Maven	`org.bouncycastle:bcprov-debug-jdk14`	≥ 1.59	No fix
☕Maven	`org.bouncycastle:bcprov-debug-jdk15to18`	≥ 1.59	No fix
☕Maven	`org.bouncycastle:bcprov-debug-jdk18on`	≥ 1.59	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.bouncycastle:bcprov-jdk14, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for GHSA-574f-3g2m-x479; check the affected-versions list above or the advisory for the patched release of org.bouncycastle:bcprov-jdk14, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

To exploit this flaw, an attacker needs to capture ciphertext encrypted by the `GOSTCTR` implementation where the `G3413CTRBlockCipher` processed more than 255 blocks of data, resulting in keystream reuse. An attack typically requires capturing these overlapping ciphertexts to perform cryptanalysis and uncover the…

Workaround published by Red Hat

To mitigate this vulnerability, strictly limit the payload encrypted under a single key and Initialization Vector (IV) pair using the GOSTCTR implementation and G3413CTRBlockCipher to a maximum of 255 blocks. Alternatively, transition to a more secure, standardized and authenticated encryption mode.

Source: Red Hat security advisory for GHSA-574f-3g2m-x479 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat AMQ Broker 7.12.7	`bcprov-jdk18on`	RHSA-2026:14276
Red Hat AMQ Broker 7.13.5	`bcprov-jdk18on`	RHSA-2026:14272
Red Hat AMQ Broker 7.14.1	`bcprov-jdk18on`	RHSA-2026:66488
Red Hat Build of Apache Camel 4.14 for Quarkus 3.27	`bcprov-jdk18on`	RHSA-2026:13631
Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14	`bcprov-debug-jdk15on`	RHSA-2026:17668
Red Hat build of Quarkus 3.20.6.SP1	`org.bouncycastle/bcprov-jdk18on:1.84.0.redhat-00001`	RHSA-2026:11720
Red Hat build of Quarkus 3.27.3.SP1	`org.bouncycastle/bcprov-jdk18on:1.84.0.redhat-00001`	RHSA-2026:11721
Red Hat JBoss Enterprise Application Platform 7.4.25	`bcprov-jdk12`	RHSA-2026:53806

Frequently Asked Questions

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).

O3 Security · Impact-Aware SCA

Is GHSA-574f-3g2m-x479 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works