CVE-2025-59037 — duckdb
CVE-2025-59037 is a CWE-506 vulnerability in duckdb. A fix is available for duckdb — see the affected versions and patch details below.
DuckDB NPM packages 1.3.3 and 1.29.2 briefly compromised with malware
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-59037.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
duckdbnpm@duckdb/node-apinpm@duckdb/node-bindingsnpmDescription
DuckDB is an analytical in-process SQL database management system. On 08 September 2025, the DuckDB distribution for Node.js on npm was compromised with malware (along with several other packages). An attacker published new versions of four of DuckDB's packages that included malicious code to interfere with cryptocoin transactions* According to the npm statistics, nobody has downloaded these packages before they were deprecated. The packages and versions @duckdb/[email protected], @duckdb/[email protected], [email protected], and @duckdb/[email protected] were affected. DuckDB immediately deprecated the specific versions, engaged npm support to delete the affected verions, and re-released the node packages with higher version numbers (1.3.4/1.30.0). Users may upgrade to versions 1.3.4, 1.30.0, or a higher version to protect themselves. As a workaround, they may also downgrade to 1.3.2 or 1.29.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | duckdb | ≥ 1.3.3&&< 1.3.4 | 1.3.4npm install duckdb@1.3.4 |
| 📦npm | @duckdb/node-api | ≥ 1.3.3&&< 1.3.4-alpha.27 | 1.3.4-alpha.27npm install @duckdb/node-api@1.3.4-alpha.27 |
| 📦npm | @duckdb/node-bindings | ≥ 1.3.3&&< 1.3.4-alpha.27 | 1.3.4-alpha.27npm install @duckdb/node-bindings@1.3.4-alpha.27 |
| 📦npm | @duckdb/duckdb-wasm | ≥ 1.29.2&&< 1.30.0 | 1.30.0npm install @duckdb/duckdb-wasm@1.30.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for duckdb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update duckdb to 1.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-59037 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-59037 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-59037. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-59037 in your dependencies?
O3 Security finds CVE-2025-59037 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.