Use of a Broken or Risky Cryptographic Algorithm Affecting duckdb/duckdb package, versions [1.4.0,1.4.2)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Use of a Broken or Risky Cryptographic Algorithm vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-UNMANAGED-DUCKDBDUCKDB-13925140
- published13 Nov 2025
- disclosed12 Nov 2025
- creditSławek Kosowski, Greg Rubin
Introduced: 12 Nov 2025
NewCVE-2025-64429 (opens in a new tab)How to fix?
Upgrade duckdb/duckdb to version 1.4.2 or higher.
Overview
Affected versions of this package are vulnerable to Use of a Broken or Risky Cryptographic Algorithm due to the use of an insecure random number generator and improper handling of cryptographic keys and initialization vectors. An attacker can compromise cryptographic keys, bypass integrity checks, or influence the random number generation process by modifying the database header, exploiting public IVs, or accessing process memory.