Cockroachdb End of Life Dates

other

Cockroachdb has been a reliable solution for developers seeking a resilient and scalable database management system since its inception. This open-source database is designed to handle large amounts of data and provide high availability, making it a popular choice among developers. The Cockroachdb community and its maintainers continually work to improve the database, ensuring it stays up-to-date with the latest security patches and features. Developers rely on Cockroachdb for its ability to handle distributed transactions and provide strong consistency guarantees, making it an essential tool for building robust and fault-tolerant applications.

The end-of-life landscape for Cockroachdb is complex, with a total of 23 versions released to date. Out of these, 18 versions have reached their end-of-life, and 5 remain actively supported. The latest stable version, 25.1.10, is the current benchmark for developers. However, version 26.1 is set to expire on 2026-08-02, marking the next significant milestone in the Cockroachdb lifecycle. Recently, version 24.3 reached its end-of-life on 2026-05-18, emphasizing the need for developers to stay informed about upcoming expiration dates to plan their upgrades and ensure uninterrupted support.

With no known CVEs tracked, Cockroachdb presents a remarkably secure profile, boasting zero critical vulnerabilities. As a result, there is no most affected version, and the database is not listed on the Known Exploited Vulnerabilities catalog. This pristine security record is a testament to the dedication of the Cockroachdb community and its maintainers. Despite this, developers should remain vigilant and stay informed about future security updates to ensure the continued integrity of their applications. By tracking end-of-life dates and staying up-to-date with the latest supported versions, developers can leverage Cockroachdb's capabilities while minimizing potential security risks.

Last updated: Oct 23, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
26.3 Aug 19, 2026Feb 19, 2027Feb 19, 2027in 119d26.3.0—Active
26.2 LTSApr 27, 2026Sep 23, 2027Sep 23, 2028in 701d26.2.9—Active
26.1 Feb 2, 2026Aug 2, 2026Aug 2, 202682d ago26.1.8—EOL
25.4 LTSNov 3, 2025May 3, 2027May 3, 2028in 558d25.4.18—Active
25.3 Aug 4, 2025Feb 4, 2026Feb 4, 2026261d ago25.3.7—EOL
25.2 LTSMay 9, 2025Dec 17, 2026Dec 17, 2027in 420d25.2.25—Active
25.1 Feb 18, 2025Aug 18, 2025Aug 18, 2025431d ago25.1.10—EOL
24.3 LTSNov 18, 2024May 5, 2026May 5, 2027in 194d24.3.37—Active
24.2 Aug 12, 2024Feb 12, 2025Feb 12, 2025618d ago24.2.10—EOL
24.1 LTSMay 20, 2024Oct 21, 2025Oct 21, 20262d ago24.1.34—EOL
23.2 LTSFeb 5, 2024Jul 8, 2025Jul 8, 2026107d ago23.2.31—EOL
23.1 LTSMay 15, 2023Nov 13, 2024Nov 13, 2025344d ago23.1.30—EOL
22.2 Dec 5, 2022Dec 5, 2023Jun 5, 2024870d ago22.2.19—EOL
22.1 May 24, 2022May 24, 2023Nov 24, 20231064d ago22.1.22—EOL
21.2 Nov 16, 2021Nov 16, 2022May 16, 20231256d ago21.2.17—EOL
21.1 May 18, 2021May 18, 2022Nov 18, 20221435d ago21.1.21—EOL
20.2 Nov 10, 2020Nov 10, 2021May 10, 20221627d ago20.2.19—EOL
20.1 May 12, 2020May 12, 2021Nov 12, 20211806d ago20.1.17—EOL
19.2 Nov 12, 2019Nov 12, 2020May 12, 20211990d ago19.2.12—EOL
19.1 Apr 30, 2019Apr 30, 2020Oct 30, 20202184d ago19.1.11—EOL
2.1 Oct 30, 2018Oct 30, 2019Apr 30, 20202367d ago2.1.11—EOL
2.0 Apr 4, 2018Apr 4, 2019Oct 4, 20192576d ago2.0.7—EOL
1.1 Oct 12, 2017Oct 12, 2018Apr 12, 20192751d ago1.1.9—EOL
1.0 May 10, 2017May 10, 2018Nov 10, 20182904d ago1.0.7—EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions