[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fSiKJ8XM9a4-QIEHwxrtCDH_wyFvhTCsxk5Qtq8hi2tc":3},{"product":4,"cycleMajor":14,"releases":15,"cves":55,"nextMajor":9},{"id":5,"slug":6,"name":7,"category":8,"vendor":9,"description":10,"logo_url":11,"official_url":9,"synced_at":12,"created_at":13},"e9915e56-de8a-4eb6-b863-7e52a0daccf4","duckdb","Duckdb","other",null,"Developers rely on Duckdb, a popular open-source columnar database management system, to efficiently manage and analyze large datasets. Created to solve the problem of slow query performance in traditional databases, Duckdb has been maintained by a community of contributors since its inception. With its ability to provide fast and efficient data processing, Duckdb has become a go-to solution for many developers. The fact that it is open-source and free to use has made it an attractive option for many projects, allowing developers to focus on building their applications without worrying about the underlying database infrastructure.\n\nThe end-of-life landscape for Duckdb is relatively straightforward, with a total of six versions released so far. Out of these, four versions have already reached their end-of-life, while two are still actively supported. The latest stable version, 1.4.4, is the recommended version for new projects. However, version 1.4 is nearing its end-of-life, with support set to expire on September 16, 2026. This means that developers still using version 1.4 should start planning their upgrades to a newer version to ensure they continue to receive security updates and bug fixes. The last version to reach end-of-life was version 1.3, which expired on September 16, 2025.\n\nFrom a security perspective, Duckdb has a clean track record, with no known CVEs reported to date. This is a testament to the dedication of the community contributors who maintain the project. As a result, there is no most affected version, and no critical CVEs to speak of. Additionally, since there are no known vulnerabilities, Duckdb is not listed on the Known Exploited Vulnerabilities catalog. Despite this, developers should still prioritize keeping their Duckdb installations up to date to ensure they have the latest security patches and features. By doing so, they can minimize their exposure to potential security risks and ensure the continued stability and performance of their applications.","https:\u002F\u002Fcdn.simpleicons.org\u002Fduckdb","2026-06-14T02:03:05.74+00:00","2026-05-30T16:23:55.845073+00:00","1",[16,24,32,38,44,50],{"id":17,"product_id":5,"cycle":18,"release_date":19,"eol":9,"eol_boolean":20,"latest":21,"latest_release_date":22,"lts":20,"support":9,"created_at":23},"a02a3700-00ee-4c61-a7d4-0568fa746898","1.5","2026-03-09",false,"1.5.3","2026-05-20","2026-05-30T16:26:10.291906+00:00",{"id":25,"product_id":5,"cycle":26,"release_date":27,"eol":28,"eol_boolean":9,"latest":29,"latest_release_date":30,"lts":31,"support":9,"created_at":23},"c7a30187-3cc2-4b6f-a999-a44e19f9f9dc","1.4","2025-09-16","2026-09-16","1.4.4","2026-01-26",true,{"id":33,"product_id":5,"cycle":34,"release_date":35,"eol":27,"eol_boolean":9,"latest":36,"latest_release_date":37,"lts":20,"support":9,"created_at":23},"a5589f1e-e844-48a2-84b1-43cd1db7fe3f","1.3","2025-05-21","1.3.2","2025-07-08",{"id":39,"product_id":5,"cycle":40,"release_date":41,"eol":35,"eol_boolean":9,"latest":42,"latest_release_date":43,"lts":20,"support":9,"created_at":23},"d0aa5413-46b3-46cd-b344-906540201891","1.2","2025-02-05","1.2.2","2025-04-08",{"id":45,"product_id":5,"cycle":46,"release_date":47,"eol":41,"eol_boolean":9,"latest":48,"latest_release_date":49,"lts":20,"support":9,"created_at":23},"6f3d3c2c-b465-4beb-9a2c-8ca96d91e9be","1.1","2024-09-09","1.1.3","2024-11-04",{"id":51,"product_id":5,"cycle":52,"release_date":53,"eol":47,"eol_boolean":9,"latest":54,"latest_release_date":53,"lts":20,"support":9,"created_at":23},"64bfbe7d-158c-442e-9846-52d296a953b2","1.0","2024-06-03","1.0.0",[]]