Complete end-of-life dates, support windows, and security status for all Duckdb versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
⚡Duckdb 1.4 reaches end of life on September 16, 2026. Plan your migration now — 130 days remaining.
Latest Active
1.5.2
1.5 series
Next EOL
1.4
Sep 16, 2026
Active Versions
1
of 6 total
EOL Versions
4
no longer patched
Release Cycle Timeline
■ EOL
■ Warning
■ Active
┊ Today
All Versions
Version
Latest Release
Release Date
EOL Date
Days
Status
1.0
1.0.0
Jun 3, 2024
Sep 9, 2024
607 days past EOL
EOL
1.1
1.1.3
Sep 9, 2024
Feb 5, 2025
458 days past EOL
EOL
1.2
1.2.2
Feb 5, 2025
May 21, 2025
353 days past EOL
EOL
1.3
1.3.2
May 21, 2025
Sep 16, 2025
235 days past EOL
EOL
1.4 LTS
1.4.4
Sep 16, 2025
Sep 16, 2026
130 days remaining
Warning
1.5
1.5.2
Mar 9, 2026
Already EOL
Supported
Active
What does Duckdb end of life mean for your organization?
When a Duckdb version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Duckdb should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Check your full stack for EOL risk
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
The next Duckdb version reaching EOL is 1.4 on September 16, 2026. See the full table above for all version EOL dates.
What is the latest supported version of Duckdb?
The latest active version of Duckdb is 1.5.2. Always verify against the table above as support windows can change.
What happens when Duckdb reaches end of life?
When Duckdb reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Duckdb?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Duckdb versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.