CockroachDB End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all CockroachDB versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.7 | May 10, 2017 | Nov 10, 2018 | 2782 days past EOL | EOL |
| 1.1 | 1.1.9 | Oct 12, 2017 | Apr 12, 2019 | 2629 days past EOL | EOL |
| 2.0 | 2.0.7 | Apr 4, 2018 | Oct 4, 2019 | 2454 days past EOL | EOL |
| 2.1 | 2.1.11 | Oct 30, 2018 | Apr 30, 2020 | 2245 days past EOL | EOL |
| 19.1 | 19.1.11 | Apr 30, 2019 | Oct 30, 2020 | 2062 days past EOL | EOL |
| 19.2 | 19.2.12 | Nov 12, 2019 | May 12, 2021 | 1868 days past EOL | EOL |
| 20.1 | 20.1.17 | May 12, 2020 | Nov 12, 2021 | 1684 days past EOL | EOL |
| 20.2 | 20.2.19 | Nov 10, 2020 | May 10, 2022 | 1505 days past EOL | EOL |
| 21.1 | 21.1.21 | May 18, 2021 | Nov 18, 2022 | 1313 days past EOL | EOL |
| 21.2 | 21.2.17 | Nov 16, 2021 | May 16, 2023 | 1134 days past EOL | EOL |
| 22.1 | 22.1.22 | May 24, 2022 | Nov 24, 2023 | 942 days past EOL | EOL |
| 22.2 | 22.2.19 | Dec 5, 2022 | Jun 5, 2024 | 748 days past EOL | EOL |
| 23.1 LTS | 23.1.30 | May 15, 2023 | Nov 15, 2024 | 585 days past EOL | EOL |
| 23.2 LTS | 23.2.30 | Feb 5, 2024 | Aug 5, 2025 | 322 days past EOL | EOL |
| 24.1 LTS | 24.1.30 | May 20, 2024 | Nov 20, 2025 | 215 days past EOL | EOL |
| 24.2 | 24.2.10 | Aug 12, 2024 | Feb 12, 2025 | 496 days past EOL | EOL |
| 24.3 | 24.3.33 | Nov 18, 2024 | May 18, 2026 | 36 days past EOL | EOL |
| 25.1 | 25.1.10 | Feb 18, 2025 | TBD | Supported | Active |
| 25.2 | 25.2.19 | May 9, 2025 | Nov 12, 2026 | 142 days remaining | Warning |
| 25.3 | 25.3.7 | Aug 4, 2025 | Feb 4, 2026 | 139 days past EOL | EOL |
| 25.4 | 25.4.11 | Nov 3, 2025 | May 3, 2027 | 314 days remaining | Active |
| 26.1 | 26.1.5 | Feb 2, 2026 | Aug 2, 2026 | 40 days remaining | Warning |
| 26.2 | 26.2.2 | Apr 27, 2026 | Oct 27, 2027 | 491 days remaining | Active |
What does CockroachDB end of life mean for your organization?
When a version of CockroachDB reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL CockroachDB should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL CockroachDB versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →