Skip to main content

Java CVE-2025-14813

| EUVDEUVD-2025-209467 CRITICAL
Use of a Broken or Risky Cryptographic Algorithm (CWE-327)
2026-04-15 bcorg GHSA-574f-3g2m-x479
9.3
CVSS 4.0 · Vendor: bcorg
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Approved algorithm selection
Exploitation Conditions

Applications must use Bouncy Castle BC-JAVA versions 1.59 through 1.83 AND specifically invoke the G3413CTRBlockCipher class for GOST R 34.13-2015 CTR mode encryption. Exploitation requires processing plaintext or ciphertext inputs exceeding 255 blocks (approximately 4KB for 128-bit GOST, 2KB for 64-bit variants depending on specific GOST algorithm variant). The attacker must have local access to either submit data for encryption through the vulnerable application or access encrypted outputs to analyze the cryptographic failure pattern.

Impact

The CVSS 9.4 score (CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N) indicates critical severity with local attack vector, low complexity, and no privilege or user interaction requirements. The high confidentiality (VC:H/SC:H) and integrity (VI:H/SI:H) impacts reflect that encrypted data beyond 255 blocks will be incorrectly processed, potentially exposing plaintext or corrupting ciphertext. However, real-world risk depends heavily on deployment context. The local attack vector (AV:L) means exploitation requires the attacker to control or influence the data being encrypted/decrypted on the same system, not remote network exploitation. No CISA KEV listing indicates no confirmed active exploitation in the wild. No EPSS score provided, but exploitation likelihood is moderate-requires applications specifically using GOST CTR mode (uncommon outside Russia/CIS countries) and processing messages exceeding 255 blocks. The deterministic nature of the flaw means it affects all instances equally, but GOST adoption is limited compared to AES, reducing attack surface. Priority should be high for organizations using GOST encryption in regulated industries (Russian government, financial services), moderate for general enterprise with BC-JAVA dependency audits.

Exploit ScenarioDerived

An application uses Bouncy Castle BC-JAVA 1.78 to encrypt sensitive financial transaction logs using GOST R 34.13-2015 CTR mode before storing them in a database. A local attacker with read access to the encrypted database files crafts a malicious input that forces the application to encrypt a transaction batch exceeding 255 blocks (e.g., 5KB log file). The cryptographic implementation silently fails to process blocks 256 and beyond correctly, either producing predictable ciphertext patterns or failing to properly encrypt portions of the plaintext. The attacker analyzes the corrupted ciphertext, extracts partially exposed plaintext from the improperly processed blocks, or manipulates the corrupted sections to alter transaction records upon decryption without detection. Publicly available exploit code exists for triggering the block counter overflow condition through crafted input sizes.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 15, 2026

GOST CTR block cipher in Bouncy Castle BC-JAVA processes only the first 255 blocks correctly, causing silent data corruption in encryption/decryption operations for longer messages. Affects BC-JAVA versions 1.59 through 1.83, with fix available in version 1.84. Local attack vector (CVSS AV:L) with critical CVSS 9.4 score reflects potential for both confidentiality and integrity compromise when applications process GOST-encrypted data streams exceeding 255 blocks (~4KB). No KEV listing or public

Earlier versions of this analysis (1)
v1 Apr 15, 2026 - 12:37 CVSS 9.3

GOST CTR block cipher in Bouncy Castle BC-JAVA processes only the first 255 blocks correctly, causing silent data corruption in encryption/decryption operations for longer messages. Affects BC-JAVA versions 1.59 through 1.83, with fix available in version 1.84. Local attack vector (CVSS AV:L) with critical CVSS 9.4 score reflects potential for both confidentiality and integrity compromise when applications process GOST-encrypted data streams exceeding 255 blocks (~4KB). No KEV listing or public exploit identified at time of analysis, but the cryptographic flaw is deterministic and reproducible.

RemediationAI

Upgrade Bouncy Castle BC-JAVA to version 1.84 or later, which contains the fix for the G3413CTRBlockCipher block counter handling. Organizations should audit their dependency trees using tools like Maven Dependency Plugin or Gradle's dependency reports to identify all components using BC-JAVA versions 1.59-1.83. Update the dependency declaration in pom.xml (Maven) or build.gradle (Gradle) to specify org.bouncycastle:bcprov-jdk18on:1.84 or appropriate variant for your JDK version. For systems unable to immediately upgrade, consider temporary workarounds: avoid GOST CTR mode encryption for messages exceeding 255 blocks (implement message segmentation with independent encryption operations per segment), or substitute alternative GOST modes like CBC or GCM if protocol allows. Consult the official advisory at https://github.com/bcgit/bc-java/wiki/CVE-2025-14813 for implementation-specific guidance and verify fixes through regression testing of GOST encryption workflows with multi-kilobyte payloads.

Affected VersionsENISA

BC-JAVA 1.59 <1.84

Affected Packages

maven org.bouncycastle:bcprov-debug-jdk14 fix: 1.84
maven org.bouncycastle:bcprov-debug-jdk15on no fix
maven org.bouncycastle:bcprov-debug-jdk15to18 fix: 1.84
maven org.bouncycastle:bcprov-debug-jdk18on fix: 1.84
maven org.bouncycastle:bcprov-ext-debug-jdk14 no fix
maven org.bouncycastle:bcprov-ext-debug-jdk15to18 no fix
maven org.bouncycastle:bcprov-ext-debug-jdk18on no fix
maven org.bouncycastle:bcprov-ext-jdk14 no fix
maven org.bouncycastle:bcprov-ext-jdk15to18 no fix
maven org.bouncycastle:bcprov-ext-jdk18on no fix
maven org.bouncycastle:bcprov-jdk14 fix: 1.84
maven org.bouncycastle:bcprov-jdk15on no fix
maven org.bouncycastle:bcprov-jdk15to18 fix: 1.84
maven org.bouncycastle:bcprov-jdk18on fix: 1.80.2, 1.81.1, 1.84
euvd bc_java fix: 1.84

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 15 packages in maven, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability resides in G3413CTRBlockCipher.java, the Bouncy Castle implementation of GOST R 34.13-2015 CTR (Counter) mode encryption. CTR mode transforms a block cipher into a stream cipher by encrypting sequential counter values and XORing the results with plaintext. The implementation contains a counter overflow or boundary condition error that prevents correct processing beyond the 255th block. In GOST block ciphers (64-bit or 128-bit block size), this limits reliable encryption to approximately 4-16KB depending on block size. CWE-327 (Use of Broken/Risky Cryptographic Algorithm) classification reflects that while GOST itself is not inherently broken, this implementation flaw renders it cryptographically unsafe. The CPE identifies the affected library as cpe:2.3:a:legion_of_the_bouncy_castle_inc.:bc-java, a widely-deployed Java cryptographic provider used in enterprise applications, TLS implementations, and secure communication frameworks.

Know when Java gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (bcorg) PRIMARY 9.3 CRITICAL
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
SUSE 8.6 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
Red Hat 7.5 HIGH

Primary rating from Vendor (bcorg).

CVSS VectorVendor: bcorg

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
None
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
None

Lifecycle Timeline

3
CVSS changed
Apr 15, 2026 - 15:22 NVD
9.4 (CRITICAL) 9.3 (CRITICAL)
Patch released
Apr 15, 2026 - 14:30 nvd
Patch available
CVE Published
Apr 15, 2026 - 08:56 nvd
CRITICAL 9.3

DescriptionCVE.org

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.

GOSTCTR implementation unable to process more than 255 blocks correctly.

This issue affects BC-JAVA: from 1.59 before 1.84.

Blast Radius

ecosystem impact
† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth
  • 11 maven packages depend on org.bouncycastle:bcprov-jdk14 (4 direct, 7 indirect)

Ecosystem-wide dependent count for version 1.59.

Executive ViewAI

Why It Matters

Bouncy Castle (BC-JAVA) versions 1.59-1.83 contain a critical cryptographic flaw in GOST CTR mode that silently corrupts encrypted data beyond 4KB, compromising both confidentiality and integrity of sensitive messages processed by affected applications. Any organization using these library versions for GOST encryption-particularly in finance, healthcare, or government sectors-faces undetected data corruption and potential compliance violations. Immediate inventory and patching to version 1.84 is essential to prevent ongoing data integrity failures.

Business Impact: Severe
Compensating Controls

Vendor-released patch: BC-JAVA version 1.84. If immediate patching is infeasible, isolate systems using GOST CTR mode from production until patched; disable GOST cipher in configurations where alternative ciphers (AES) are acceptable; implement message size checks to reject GOST-encrypted payloads exceeding 255 blocks (~4KB) until patched.

Threat Intelligence Overview

EPSS Score
0.0%
Top 99% exploitable
Threat Intel
1
1 source
Social Media
1
Sightings
Data Quality
8 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GHSA Vendor CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
Very High
Technical Impact
Total

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

More in Java

View all
CVE-2012-4681 CRITICAL POC
9.8 Aug 28

Oracle Java SE 7 Update 6 and earlier contains multiple sandbox bypass vulnerabilities via the ClassFinder and forName m

CVE-2015-7450 CRITICAL POC
9.8 Jan 02

Remote code execution in IBM Sterling B2B Integrator, Sterling Integrator, and Tivoli Common Reporting allows unauthenti

CVE-2013-2465 CRITICAL POC
9.8 Jun 18

Java Runtime Environment sandbox bypass via incorrect image channel verification in 2D component allows remote unauthent

CVE-2011-3544 CRITICAL POC
9.8 Oct 19

Oracle Java SE JDK/JRE 7 and 6 Update 27 and earlier allows remote code execution with complete system compromise throug

CVE-2010-1871 HIGH POC
8.8 Aug 05

JBoss Seam 2 in Red Hat JBoss EAP 4.3.0 fails to sanitize JBoss Expression Language inputs, allowing remote attackers to

CVE-2012-1723 CRITICAL POC
9.8 Jun 16

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 update 4 and earlier, 6 up

CVE-2013-0422 CRITICAL POC
9.8 Jan 10

Multiple vulnerabilities in Oracle Java 7 before Update 11 allow remote attackers to execute arbitrary code by (1) using

CVE-2012-0507 CRITICAL POC
9.8 Jun 07

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Up

CVE-2015-4852 CRITICAL POC
9.8 Nov 18

The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers

CVE-2012-5076 CRITICAL POC
9.8 Oct 16

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 7 and earlier allow

CVE-2017-3066 CRITICAL POC
9.8 Apr 27

Remote unauthenticated attackers can execute arbitrary code on Adobe ColdFusion servers through Java deserialization fla

CVE-2012-0391 CRITICAL POC
9.8 Jan 08

The ExceptionDelegator component in Apache Struts before 2.2.3.1 interprets parameter values as OGNL expressions during

Vendor StatusVendor

SUSE

Severity: High
Product Status
openSUSE Tumbleweed Fixed
SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS Affected
SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS Affected
SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS Affected
SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS Affected

References

Advisories & patches
PATCH https://github.com/bcgit/bc-java/commit/701686cb0184cd9ae103c801b3581fdf95c6d4f3 PATCH https://github.com/bcgit/bc-java/commit/b42574345414e4b7c8051b16fa1fafe01c29871f ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2025-14813 ADVISORY https://vuldb.com/vuln/357692 REF https://access.redhat.com/errata/RHSA-2026:11720 REF https://access.redhat.com/errata/RHSA-2026:11721 REF https://access.redhat.com/errata/RHSA-2026:13631 REF https://access.redhat.com/errata/RHSA-2026:14272 REF https://access.redhat.com/errata/RHSA-2026:14276 REF https://access.redhat.com/errata/RHSA-2026:17668 REF https://access.redhat.com/errata/RHSA-2026:18054 REF https://access.redhat.com/errata/RHSA-2026:18055 REF https://access.redhat.com/errata/RHSA-2026:18059 REF https://access.redhat.com/errata/RHSA-2026:21772 REF https://access.redhat.com/errata/RHSA-2026:24977 REF https://access.redhat.com/errata/RHSA-2026:53644 REF https://access.redhat.com/errata/RHSA-2026:53645 REF https://access.redhat.com/errata/RHSA-2026:53646 REF https://access.redhat.com/errata/RHSA-2026:53806 REF https://access.redhat.com/errata/RHSA-2026:60239 REF https://access.redhat.com/errata/RHSA-2026:60246 REF https://access.redhat.com/errata/RHSA-2026:60247 REF https://access.redhat.com/errata/RHSA-2026:60248 REF https://access.redhat.com/errata/RHSA-2026:60249 REF https://access.redhat.com/errata/RHSA-2026:60250 REF https://access.redhat.com/errata/RHSA-2026:60251 REF https://access.redhat.com/errata/RHSA-2026:60252 REF https://access.redhat.com/errata/RHSA-2026:60254 REF https://access.redhat.com/errata/RHSA-2026:60256 REF https://access.redhat.com/errata/RHSA-2026:60259 REF https://access.redhat.com/errata/RHSA-2026:66488 REF https://access.redhat.com/security/cve/CVE-2025-14813 REF https://bugzilla.redhat.com/show_bug.cgi?id=2458640 REF https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902025%E2%80%9014813 REF https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-14813.json

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy