Vulnary
← back to the feed
Critical· 9.3official fix available

CVE-2025-14813

This vulnerability involves the use of a broken cryptographic algorithm in the Bouncy Castle Java library. Attackers who can run code on the same machine can read or modify encrypted data. The flaw is present in many older versions of the library.

publishedApr 15, 2026
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.3
critical · how bad it is
exploitation · epss
<1%
24th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 3, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Bouncy Castle BC-JAVA bcprov core modules, versions 1.59 through 1.80.1, 1.81 through 1.81.0, and 1.82 through 1.83. Users of these libraries in Java applications are affected.

02

Real-world impact

An attacker who can execute code locally can read or tamper with data protected by the library, potentially exposing sensitive information or corrupting data integrity.

03

Why this severity

The CVSS score of 9.3 reflects that the vulnerability can be exploited locally without authentication, giving an attacker high confidentiality and integrity impact, while availability is unaffected.

04

What to do about it

official fix available
recommended steps
  1. 011. Identify the current bcprov version in your application.
  2. 022. Download the latest bcprov jar from the official Bouncy Castle website (versions 1.80.2 or later, 1.81.1 or later, or 1.84 or later).
  3. 033. Replace the old jar in your application and restart the service.

NVD description

05

Timeline

  1. Apr 15, 2026 · Apr 15, 2026
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Aug 4, 2026 · 14h ago
    Advisory updated
    The NVD record was last revised.
  3. Aug 4, 2026 · 12h ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorLocal
Attack complexityLow
Attack requirementsNone
Privileges requiredNone
User interactionNone needed
Confidentiality impactHigh
Integrity impactHigh
Availability impactNone
07

References & advisories

NVD advisory ↗Search advisories ↗
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →