Cockroachdb 2.x — End of Life
EOLCockroachdb 2.x — All releases
| Version | Released | Active support | EOL date | Latest patch | Status |
|---|---|---|---|---|---|
| 2.1 | Oct 30, 2018 | Oct 30, 2019 | Apr 30, 2020 | 2.1.11 | EOL |
| 2.0 | Apr 4, 2018 | Apr 4, 2019 | Oct 4, 2019 | 2.0.7 | EOL |
CVEs affecting Cockroachdb 2.x (0)
Cockroachdb 2.x is EOL — migrate to Cockroachdb 19.x
Cockroachdb 19.x is the next major release. Plan your upgrade before Cockroachdb 2.x stops receiving security patches.
Frequently asked questions
Is Cockroachdb 2 end of life?
Yes. All Cockroachdb 2.x releases have reached end of life and no longer receive security patches. Migrate to Cockroachdb 19.x as soon as possible.
What CVEs affect Cockroachdb 2?
No CVEs are currently tracked for Cockroachdb 2.x in our database. This may mean no vulnerabilities have been recorded yet, or the data is still syncing.
What is the latest Cockroachdb 2 version?
The latest Cockroachdb 2.x patch release is 2.1.11, released on January 22, 2020. Always run the latest patch to benefit from all security fixes.
How to migrate from Cockroachdb 2 to Cockroachdb 19?
To migrate from Cockroachdb 2 to Cockroachdb 19: (1) review the official Cockroachdb 19 migration guide for breaking changes, (2) update dependencies and configuration accordingly, (3) test thoroughly in a staging environment, (4) deploy with a rollback plan. Starting early gives you time to resolve compatibility issues before your current version reaches end of life.
Is it safe to run Cockroachdb 2 in production?
No. Cockroachdb 2 has reached end of life and security vulnerabilities are no longer patched. Upgrade to a supported version immediately.
Data sourced from endoflife.date · CVE data from NVD · EPSS from FIRST.org · KEV from CISA