Duckdb 1.5 · Version Status
Duckdb 1.5 End of Life Date
Duckdb 1.5 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Duckdb 1.5 is actively supported. EOL date: Already EOL.
EOL Date
Already EOL
Supported
Latest Release
1.5.2
Standard release
Release Date
Mar 9, 2026
Duckdb 1.5 series
| 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.4 |
Sep 16, 2026 |
Warning |
| → 1.5 |
1.5.2 |
EOL |
Active |
What does Duckdb 1.5 end of life mean?
When Duckdb 1.5 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Duckdb 1.5 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Duckdb 1.5 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Duckdb 1.5 reach end of life?
Duckdb 1.5 has already reached end of life.
Is Duckdb 1.5 still supported?
Yes, Duckdb 1.5 is currently supported. The EOL date is Already EOL.
What should I upgrade to from Duckdb 1.5?
The recommended upgrade from Duckdb 1.5 is
Duckdb 1.5 — the latest actively supported version. Check the
Duckdb full timeline for all supported versions.
What are the security risks of running Duckdb 1.5 past EOL?
When Duckdb 1.5 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Duckdb should migrate immediately or implement compensating controls.