DuckDB 2.0 · Version Status
DuckDB 2.0 End of Life Date
DuckDB 2.0 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
✓
DuckDB 2.0 is actively supported. EOL date: October 21, 2027.
📅 Get reminded before DuckDB 2.0 reaches EOL on October 21, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Oct 21, 2027
364 days remaining
Latest Release
2.0.0
LTS release
Release Date
Oct 21, 2026
DuckDB 2.0 series
Where these dates come from
End of lifeOct 21, 2027endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseOct 21, 2026endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
DuckDB 2.0 was released on October 21, 2026 and support is scheduled to end on October 21, 2027 — a planned supported lifespan of 1 year, in line with the 1 year median for DuckDB LTS releases. It is a long-term support (LTS) release, so it carries a longer patch window than the interim releases around it. Its most recent patch is 2.0.0, published October 21, 2026.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
| Version | Latest | EOL Date | Status |
|---|
| 1.0 |
1.0.0 |
Sep 9, 2024 |
EOL |
| 1.1 |
1.1.3 |
Feb 5, 2025 |
EOL |
| 1.2 |
1.2.2 |
May 21, 2025 |
EOL |
| 1.3 |
1.3.2 |
Sep 16, 2025 |
EOL |
| 1.4 LTS |
1.4.5 |
Nov 17, 2026 |
Warning |
| 1.5 LTS |
1.5.6 |
Mar 1, 2027 |
Warning |
| → 2.0 LTS |
2.0.0 |
Oct 21, 2027 |
Active |
What does DuckDB 2.0 end of life mean?
When DuckDB 2.0 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running DuckDB 2.0 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to DuckDB 2.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does DuckDB 2.0 reach end of life?
DuckDB 2.0 reaches end of life on October 21, 2027. That is 364 days remaining.
Is DuckDB 2.0 still supported?
Yes, DuckDB 2.0 is currently supported. The EOL date is October 21, 2027.
What should I upgrade to from DuckDB 2.0?
The recommended upgrade from DuckDB 2.0 is
DuckDB 2.0 — the latest actively supported version. Check the
DuckDB full timeline for all supported versions.
What are the security risks of running DuckDB 2.0 past EOL?
When DuckDB 2.0 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL DuckDB should migrate immediately or implement compensating controls.