VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

duckdb: vulnerability history, versions and safety

duckdb is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 13 releases, from Jan 2024 to Nov 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H1 U3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 12 Nov 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all duckdb vulnerabilities

Vulert verdict on duckdb 2.0.1.dev2610211350 i

Updated on 23 Oct 2026

Good news: 2.0.1.dev2610211350, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 76/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

What to do: Stay on 2.0.1.dev2610211350 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.0.1.dev2610211350 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.0.1.dev2610211350 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 1 in the last year i
  • Latest disclosure 12 Nov 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 194 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for duckdb, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.0.1.dev2610211350 22 Oct 2026 none MIT — Details →
2.0.0 21 Oct 2026 none MIT — Details →
2.0.0.dev2610192346 20 Oct 2026 none MIT — Details →
2.0.0.dev2610191843 19 Oct 2026 none MIT — Details →
2.0.0.dev2610162032 17 Oct 2026 none MIT — Details →
2.0.0.dev2610161340 16 Oct 2026 none MIT — Details →
2.0.0.dev2610151406 15 Oct 2026 none MIT — Details →
2.0.0.dev2610011535 02 Oct 2026 none MIT — Details →
1.5.6 28 Sep 2026 none MIT — Details →
1.5.6.dev50 27 Sep 2026 none MIT — Details →
2.0.0.dev2609250715 25 Sep 2026 none MIT — Details →
2.0.0.dev2609242139 25 Sep 2026 none MIT — Details →
2.0.0.dev2609222040 23 Sep 2026 none MIT — Details →
1.5.6.dev48 23 Sep 2026 none MIT — Details →
2.0.0.dev2609221243 22 Sep 2026 none MIT — Details →
1.5.6.dev46 19 Sep 2026 none MIT — Details →
1.5.6.dev44 18 Sep 2026 none MIT — Details →
1.5.6.dev42 17 Sep 2026 none MIT — Details →
1.5.6.dev40 16 Sep 2026 none MIT — Details →
2.0.0.dev2609121639 12 Sep 2026 none MIT — Details →
1.5.6.dev36 10 Sep 2026 none MIT — Details →
1.5.6.dev34 07 Sep 2026 none MIT — Details →
1.6.0.dev379 02 Sep 2026 none MIT — Details →
1.5.6.dev32 02 Sep 2026 none MIT — Details →
1.5.6.dev30 29 Aug 2026 none MIT — Details →
1.6.0.dev365 20 Aug 2026 none MIT — Details →
1.5.6.dev25 20 Aug 2026 none MIT — Details →
1.6.0.dev360 19 Aug 2026 none MIT — Details →
1.5.6.dev22 19 Aug 2026 none MIT — Details →
1.6.0.dev358 18 Aug 2026 none MIT — Details →
1.5.6.dev20 18 Aug 2026 none MIT — Details →
1.5.6.dev11 29 Jul 2026 none MIT — Details →
1.5.6.dev9 28 Jul 2026 none MIT — Details →
1.6.0.dev343 28 Jul 2026 none MIT — Details →
1.5.6.dev7 26 Jul 2026 none MIT — Details →
1.6.0.dev341 26 Jul 2026 none MIT — Details →
1.6.0.dev339 25 Jul 2026 none MIT — Details →
1.5.6.dev5 25 Jul 2026 none MIT — Details →
1.6.0.dev337 24 Jul 2026 none MIT — Details →
1.5.5 22 Jul 2026 none MIT — Details →
1.6.0.dev291 19 Jul 2026 none MIT — Details →
1.5.5.dev31 19 Jul 2026 none MIT — Details →
1.5.5.dev29 18 Jul 2026 none MIT — Details →
1.6.0.dev289 18 Jul 2026 none MIT — Details →
1.6.0.dev287 17 Jul 2026 none MIT — Details →
1.5.5.dev27 17 Jul 2026 none MIT — Details →
1.5.5.dev25 16 Jul 2026 none MIT — Details →
1.6.0.dev285 16 Jul 2026 none MIT — Details →
1.6.0.dev284 15 Jul 2026 none MIT — Details →
1.5.5.dev23 15 Jul 2026 none MIT — Details →
1.5.5.dev21 10 Jul 2026 none MIT — Details →
1.6.0.dev280 05 Jul 2026 none MIT — Details →
1.6.0.dev278 04 Jul 2026 none MIT — Details →
1.5.5.dev19 04 Jul 2026 none MIT — Details →
1.6.0.dev276 02 Jul 2026 none MIT — Details →
1.6.0.dev265 02 Jul 2026 none MIT — Details →
1.5.5.dev17 02 Jul 2026 none MIT — Details →
1.6.0.dev214 01 Jul 2026 none MIT — Details →
1.5.5.dev13 28 Jun 2026 none MIT — Details →
1.6.0.dev211 27 Jun 2026 none MIT — Details →
1.5.5.dev11 27 Jun 2026 none MIT — Details →
1.6.0.dev203 26 Jun 2026 none MIT — Details →
1.6.0.dev68 26 Jun 2026 none MIT — Details →
1.5.5.dev9 26 Jun 2026 none MIT — Details →
1.6.0.dev72 22 Jun 2026 none MIT — Details →
1.5.5.dev3 19 Jun 2026 none MIT — Details →
1.6.0.dev66 19 Jun 2026 none MIT — Details →
1.6.0.dev64 18 Jun 2026 none MIT — Details →
1.5.4 17 Jun 2026 none MIT — Details →
1.4.5 17 Jun 2026 none MIT — Details →
1.5.4.dev25 16 Jun 2026 none MIT — Details →
1.4.5.dev46 13 Jun 2026 none MIT — Details →
1.5.4.dev18 11 Jun 2026 none MIT — Details →
1.4.5.dev39 10 Jun 2026 none MIT — Details →
1.4.5.dev37 09 Jun 2026 none MIT — Details →
1.5.4.dev8 06 Jun 2026 none MIT — Details →
1.4.5.dev35 30 May 2026 none MIT — Details →
1.5.4.dev6 30 May 2026 none MIT — Details →
1.4.5.dev33 29 May 2026 none MIT — Details →
1.5.4.dev2 27 May 2026 none MIT — Details →
1.5.3 20 May 2026 none MIT — Details →
1.5.3.dev26 16 May 2026 none MIT — Details →
1.4.5.dev31 14 May 2026 none MIT — Details →
1.5.3.dev24 14 May 2026 none MIT — Details →
1.5.3.dev22 13 May 2026 none MIT — Details →
1.5.3.dev19 11 May 2026 none MIT — Details →
1.5.3.dev17 09 May 2026 none MIT — Details →
1.5.3.dev13 06 May 2026 none MIT — Details →
1.5.3.dev7 23 Apr 2026 none MIT — Details →
1.4.5.dev27 22 Apr 2026 none MIT — Details →
1.5.2 13 Apr 2026 none MIT — Details →
1.5.1 23 Mar 2026 none MIT — Details →
1.6.0.dev12 20 Mar 2026 none MIT — Details →
1.5.0 09 Mar 2026 none MIT — Details →
1.4.4 26 Jan 2026 none MIT — Details →
1.4.3 09 Dec 2025 none MIT — Details →
1.4.2 12 Nov 2025 none MIT — Details →
1.4.1 07 Oct 2025 U1 MIT Yes Details →
1.4.0 16 Sep 2025 U1 MIT Yes Details →
1.3.2 08 Jul 2025 none MIT — Details →
1.3.1 16 Jun 2025 none — — Details →
1.3.0 21 May 2025 none — — Details →
1.2.2 08 Apr 2025 none — — Details →
1.2.1 05 Mar 2025 none — — Details →
0.0.0 26 Feb 2025 U2 — Yes Details →
1.2.0 05 Feb 2025 none — — Details →
1.1.3 04 Nov 2024 none — — Details →
1.1.2 14 Oct 2024 none — — Details →
1.1.1 24 Sep 2024 none — — Details →
1.1.0 09 Sep 2024 none — — Details →
1.0.0 03 Jun 2024 H1 U1 — Yes Details →
0.10.3 22 May 2024 U1 — Yes Details →
0.10.2 17 Apr 2024 U1 — Yes Details →
0.10.1 18 Mar 2024 U1 — Yes Details →
0.10.0 13 Feb 2024 U1 — Yes Details →
0.9.2 14 Nov 2023 U2 — Yes Details →
0.9.1 11 Oct 2023 U2 — Yes Details →
0.9.0 26 Sep 2023 U2 — Yes Details →
0.8.1 13 Jun 2023 U2 — Yes Details →
0.8.0 17 May 2023 U2 — Yes Details →

The newest 120 of 153 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2
  • 2025 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for duckdb

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-22682: DuckDB Extension Injection Vulnerability 9.8 critical 0.9.3.dev6 30 Jan 2024
CVE-2024-41672: DuckDB SQL Database Vulnerability Allows Unauthorized Filesystem Access 7.5 high c9b7c98aa0e1cd7363fe8bb8543a95f38e980d8a 24 Jul 2024
CVE-2024-41672: DuckDB Filesystem Access Vulnerability via sniff_csv Function 7.5 high 1.1.0 21 Jan 2025
CVE-2025-64429: DuckDB Vulnerability in Block-Based Encryption Implementation 6.5 medium 1.4.2 12 Nov 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About duckdb

Is duckdb safe to use?

Vulert records 4 vulnerabilities for duckdb in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 3 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is duckdb's Vulert package health score?

Vulert scores duckdb 76/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of duckdb affected?

No. 2.0.1.dev2610211350, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does duckdb have?

4 vulnerabilities are recorded for duckdb in the PyPI ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 3 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new duckdb vulnerabilities disclosed?

1 vulnerability was recorded for duckdb in the last 12 months, and the oldest entry in this database dates to 30 Jan 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of duckdb are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor duckdb for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the duckdb version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.