Cockroachdb 2.0 · Version Status
Cockroachdb 2.0 End of Life Date
Cockroachdb 2.0 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Cockroachdb 2.0 is past end of life. This version no longer receives security patches. 2409 days past EOL — migrate to a supported version immediately.
EOL Date
Oct 4, 2019
2409 days past EOL
Latest Release
2.0.7
Standard release
Release Date
Apr 4, 2018
Cockroachdb 2.0 series
| Version | Latest | EOL Date | Status |
|---|
| 1.0 |
1.0.7 |
Nov 10, 2018 |
EOL |
| 1.1 |
1.1.9 |
Apr 12, 2019 |
EOL |
| → 2.0 |
2.0.7 |
Oct 4, 2019 |
EOL |
| 2.1 |
2.1.11 |
Apr 30, 2020 |
EOL |
| 19.1 |
19.1.11 |
Oct 30, 2020 |
EOL |
| 19.2 |
19.2.12 |
May 12, 2021 |
EOL |
| 20.1 |
20.1.17 |
Nov 12, 2021 |
EOL |
| 20.2 |
20.2.19 |
May 10, 2022 |
EOL |
What does Cockroachdb 2.0 end of life mean?
When Cockroachdb 2.0 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Cockroachdb 2.0 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Cockroachdb 26.2 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Cockroachdb 2.0 reach end of life?
Cockroachdb 2.0 reached end of life on October 4, 2019. This version is no longer receiving security patches.
Is Cockroachdb 2.0 still supported?
No. Cockroachdb 2.0 reached end of life on October 4, 2019 and is no longer receiving security patches.
What should I upgrade to from Cockroachdb 2.0?
The recommended upgrade from Cockroachdb 2.0 is
Cockroachdb 26.2 — the latest actively supported version. Check the
Cockroachdb full timeline for all supported versions.
What are the security risks of running Cockroachdb 2.0 past EOL?
When Cockroachdb 2.0 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Cockroachdb should migrate immediately or implement compensating controls.