← Back to results
Vulnerability record · public intelligence
CVE-2025-14813
CRITICAL

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

Published Apr 15, 2026 · Updated Nov 3, 2026

Severity · CVSSCRITICAL · Not scored
Known exploitationNot listed
EPSS / likelihood0.32%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Nov 3, 2026

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

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

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

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

FIRST-EPSSCVE-LIST-V5
SSVC priority
MEDIUM
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. GitHub advisory ↗
  2. Patch commit ↗
  3. Patch commit ↗
  4. access.redhat.com ↗
  5. access.redhat.com ↗
  6. access.redhat.com ↗
  7. access.redhat.com ↗
  8. access.redhat.com ↗
  9. access.redhat.com ↗
  10. access.redhat.com ↗
  11. access.redhat.com ↗
  12. access.redhat.com ↗

Record history

Published Apr 15, 2026 · Last refreshed Nov 3, 2026

Related intelligence
Browse all vulnerabilities →
CVE-2026-11165CRITICAL

CVE-2026-11165

Related through FIRST-EPSS and CVE-LIST-V5 evidence

Use after free in WebMIDI in Google Chrome on iOS prior to 149.0.7827.53 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)

CVE-2026-11009CRITICAL

CVE-2026-11009

Related through FIRST-EPSS and CVE-LIST-V5 evidence

Use after free in USB in Google Chrome on Windows prior to 149.0.7827.53 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)

CVE-2026-110130CRITICAL

Dockhand before 1.0.45 Authentication Bypass via Static-Asset Check

Related through FIRST-EPSS and CVE-LIST-V5 evidence

Dockhand before 1.0.45 Authentication Bypass via Static-Asset Check

CVE-2026-11047CRITICAL

CVE-2026-11047

Related through FIRST-EPSS and CVE-LIST-V5 evidence

Inappropriate implementation in Base in Google Chrome on Windows prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)