Widely used cryptographic library (Bouncy Castle BC-JAVA bcprov) with a CTR mode vulnerability; could affect many Java-based crypto operations across industries.
CVE-2025-14813
CRITICAL: BC-JAVA bcprov GOSTCTR CTR block limit 255.
Is CVE-2025-14813 being exploited?
Not confirmed. CVE-2025-14813 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.31% probability of exploitation in the next 30 days.
How severe is CVE-2025-14813?
CVE-2025-14813 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-14813?
Yes. A fix has been recorded for CVE-2025-14813. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-14813 affect?
CVE-2025-14813 affects BC-JAVA bcprov (Bouncy Castle) 1.59-1.83. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2025-14813?
Upgrade to BC-JAVA bcprov 1.84+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crypto weakness in GOSTCTR processing may cause encryption/decryption errors or data leakage when CTR blocks exceed 255.
Patch when possible
- affected>= 1.59 and < 1.80.2
- affected>= 1.81 and < 1.81.1
- affected>= 1.82 and < 1.84
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.