DuckDB 1.3
DuckDB 1.3
The DuckDB 1.3 reached end of service life on Sep 16, 2025 — DuckDB no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your DuckDB 1.3 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.3
- product Label
- DuckDB
- release Label
- 1.3
- codename
- Ossivalis
- lts
- latest Version
- 1.3.2
- release Date
- 2025-05-21
- maintained
- source Url
- https://endoflife.date/duckdb
Lifecycle Dates
- End of Service Life
- Sep 16, 2025
- Last OEM Support
- Sep 16, 2025
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for DuckDB 1.3 — 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.3?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for DuckDB 1.3 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.3 Support: Frequently Asked Questions
Is the DuckDB 1.3 still supported?
DuckDB ended support for the DuckDB 1.3 on Sep 16, 2025 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the DuckDB 1.3 end of service life (EOSL) date?
DuckDB lists the end of service life for the DuckDB 1.3 as Sep 16, 2025.
Can I keep using the DuckDB 1.3 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.3 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location. You get an indicative price within 24 hours and a firm quote within 48.
Known Vulnerabilities Affecting DuckDB 1.3
1 published CVE affects the DuckDB 1.3, including 1 rated critical or high severity. DuckDB no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2026-111497 | CRITICAL | 9.2 | Oct 22, 2026 | A buffer overflow vulnerability in the Brotli decoder (c/dec/decode.c) in Google Brotli versions 1.0.3 through 1.2.0 on all platforms allows a remote unauthenticated attacker to corrupt adjacent decoder state memory, disclose sensitive memory contents, cause a denial of service, or potentially execute arbitrary code using a crafted Brotli-compressed stream. Users need to update any Brotli libraries or binaries between 1.0.3 through 1.2.0 to the latest available version: 1.0.10 or 1.1.1 or 1 |