Synced 02 Nov 2026 13:39 UTC Account
← All products

DuckDB ↗

DuckDB · Database
↻ RSS feed
Monitors DuckDB and tailors your dashboard to that exact version.
2.0.0 · latest cycle20/100 Critical · exploited

Summary iPlain-English security verdict for DuckDB, generated from its current health score, actively-exploited vulnerabilities, and latest supported version.

DuckDB currently scores 20/100 — critical, with active exploitation. 1 of its known vulnerability is being actively exploited in the wild (CISA KEV), including CVE-2026-111497. The latest supported release is 2.0.0. Upgrade immediately and review your exposure to the actively-exploited CVEs below.

Disclosure trend iNew CVEs published for DuckDB each year (NVD). A higher bar means more disclosures that year — more scrutiny, not necessarily less safe.

'19
'20
'21
'22
'23
'24
'25
'26

Patch priority — what to act on iThe issues to fix first — actively exploited (CISA KEV) first, then by exploitation probability (EPSS), then severity. Each row's "→ fixed in" is the earliest version that patches it; "see advisory" means no fixed version is published.

Most urgent first — actively exploited, then likeliest to be exploited.

CVE-2026-111497 CRITICAL exploited CWE-252 EPSS 83% → see advisory

Get alerted about DuckDB

Be emailed the moment DuckDB gets a newly exploited vulnerability (CISA KEV) or a release reaches end of life. Free · double opt-in · unsubscribe anytime.

We email only on real events for DuckDB — no marketing, no sharing, and we never know what you run. Track your whole stack →

★ Monitor up to 200 products — freeHit ☆ Monitor on anything you run, then sign in (no password) to sync your stack across devices and unlock smart insights, risk history & CSV/JSON exports. Sign in free →

Versions & lifecycle iWhen each release line stops receiving security patches (end-of-life). After EOL there are no more fixes — plan upgrades before these dates.

How long each DuckDB release line is supported — and when it sunsets. Select a line for its full report.

Oct21'27 DuckDB 2.0EOL 2027-10-21
Mar1'27 DuckDB 1.5EOL 2027-03-01
Nov17'26 DuckDB 1.4EOL 2026-11-17
Sept16'25 DuckDB 1.3ended 2025-09-16
May21'25 DuckDB 1.2ended 2025-05-21
Feb5'25 DuckDB 1.1ended 2025-02-05
Sept9'24 DuckDB 1.0ended 2024-09-09

Full DuckDB end-of-life dates & support timeline →

2.0 latest 2.0.0 Supported until 2027-10-212.0.0 → 1.5 latest 1.5.6 Supported until 2027-03-011.5.6 → 1.4 latest 1.4.5 Supported until 2026-11-171.4.5 → 1.3 latest 1.3.2 End of life ended 2025-09-161.3.2 → 1.2 latest 1.2.2 End of life ended 2025-05-211.2.2 → 1.1 latest 1.1.3 End of life ended 2025-02-051.1.3 → 1.0 latest 1.0.0 End of life ended 2024-09-091.0.0 → See all upcoming end-of-life dates →

Frequently asked

Is DuckDB safe and patched?

DuckDB currently scores 20/100 — critical, with active exploitation. 1 of its known vulnerability is being actively exploited in the wild (CISA KEV), including CVE-2026-111497. The latest supported release is 2.0.0. Upgrade immediately and review your exposure to the actively-exploited CVEs below.

What should I do about DuckDB now?

Upgrade DuckDB to the latest supported release (2.0.0) or later, which clears the actively-exploited issues affecting older versions, then confirm against DuckDB's official advisory.

When does DuckDB reach end-of-life?

The latest supported DuckDB release is 2.0.0. After end-of-life a release no longer receives security patches.

Which versions of DuckDB are still receiving security updates?

Supported DuckDB release lines (latest 2.0.0): 2.0, 1.5, 1.4. End-of-life releases no longer receive security patches.

Similar software we track

Other Database products — compare their security status.

Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against DuckDB's official advisory before you patch or upgrade — DuckDB official site ↗