Cockroachdb 24.x — End of Life
EOLCockroachdb 24.x — All releases
| Version | Released | Active support | EOL date | Latest patch | Status |
|---|---|---|---|---|---|
| 24.3 | Nov 18, 2024 | Nov 18, 2025 | May 18, 2026 | 24.3.33 | EOL |
| 24.2 | Aug 12, 2024 | Feb 12, 2025 | Feb 12, 2025 | 24.2.10 | EOL |
| 24.1LTS | May 20, 2024 | May 20, 2025 | Nov 20, 2025 | 24.1.29 | EOL |
CVEs affecting Cockroachdb 24.x (0)
Cockroachdb 24.x is EOL — migrate to Cockroachdb 25.x
Cockroachdb 25.x is the next major release. Plan your upgrade before Cockroachdb 24.x stops receiving security patches.
Frequently asked questions
Is Cockroachdb 24 end of life?
Yes. All Cockroachdb 24.x releases have reached end of life and no longer receive security patches. Migrate to Cockroachdb 25.x as soon as possible.
What CVEs affect Cockroachdb 24?
No CVEs are currently tracked for Cockroachdb 24.x in our database. This may mean no vulnerabilities have been recorded yet, or the data is still syncing.
What is the latest Cockroachdb 24 version?
The latest Cockroachdb 24.x patch release is 24.3.33, released on May 20, 2026. Always run the latest patch to benefit from all security fixes.
How to migrate from Cockroachdb 24 to Cockroachdb 25?
To migrate from Cockroachdb 24 to Cockroachdb 25: (1) review the official Cockroachdb 25 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 24 in production?
No. Cockroachdb 24 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