DuckDB 1.4 (LTS)
DuckDB 1.4 (LTS)
The DuckDB 1.4 (LTS) reaches end of service life on Sep 16, 2026. Third-party support keeps it managed past that date — issue management, vulnerability remediation, and compliance maintenance from 24/7 engineers.
24/7 engineers own your DuckDB 1.4 (LTS) incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- duckdb
- release
- 1.4
- product Label
- DuckDB
- release Label
- 1.4 (LTS)
- codename
- Andium
- lts
- true
- latest Version
- 1.4.5
- release Date
- 2025-09-16
- maintained
- true
- source Url
- https://endoflife.date/duckdb
Lifecycle Dates
- End of Service Life
- Sep 16, 2026
- Last OEM Support
- Sep 16, 2026
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for DuckDB 1.4 (LTS) — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for DuckDB 1.4 (LTS)?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for DuckDB 1.4 (LTS) when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
DuckDB 1.4 (LTS) Support: Frequently Asked Questions
Is the DuckDB 1.4 (LTS) still supported?
Yes, but DuckDB support for the DuckDB 1.4 (LTS) ends on Sep 16, 2026. You can upgrade on the vendor's schedule, or move to third-party support and keep the release you're on — issues managed, vulnerabilities remediated, compliance maintained.
When is the DuckDB 1.4 (LTS) end of service life (EOSL) date?
DuckDB lists the end of service life for the DuckDB 1.4 (LTS) as Sep 16, 2026.
Can I keep using the DuckDB 1.4 (LTS) after its EOSL date?
Yes. EOSL means DuckDB stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the DuckDB 1.4 (LTS) cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting DuckDB 1.4 (LTS)
1 published CVE affects the DuckDB 1.4 (LTS). Our 24/7 engineers help you assess exposure, prioritize fixes and apply available patches.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2025-64429 | MEDIUM | 6.9 | Nov 12, 2025 | DuckDB is a SQL database management system. DuckDB implemented block-based encryption of DB on the filesystem starting with DuckDB 1.4.0. There are a few issues related to this implementation. The DuckDB can fall back to an insecure random number generator (pcg32) to generate cryptographic keys or IVs. When clearing keys from memory, the compiler may remove the memset() and leave sensitive data on the heap. By modifying the database header, an attacker could downgrade the encryption mode from GC |