CockroachDB 21.2 · Version Status
CockroachDB 21.2 End of Life Date
CockroachDB 21.2 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
CockroachDB 21.2 is past end of life. This version no longer receives security patches. 1249 days past EOL — migrate to a supported version immediately.
EOL Date
May 16, 2023
1249 days past EOL
Latest Release
21.2.17
Standard release
Release Date
Nov 16, 2021
CockroachDB 21.2 series
Lifecycle detail
CockroachDB 21.2 was released on November 16, 2021 and support ended on May 16, 2023 — a supported lifespan of 1 year and 6 months, in line with the 1 year and 6 months median for CockroachDB releases. It was not an LTS release; CockroachDB reserves longer patch windows for its LTS versions. The last patch it will ever receive is 21.2.17, published October 12, 2022 — 7 months before support ended. It has been without security patches for 3 years and 5 months. 11 newer CockroachDB releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended CockroachDB 21.2 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| 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 21.2 end of life mean?
When CockroachDB 21.2 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running CockroachDB 21.2 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
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 21.2 reach end of life?
CockroachDB 21.2 reached end of life on May 16, 2023. This version is no longer receiving security patches.
Is CockroachDB 21.2 still supported?
No. CockroachDB 21.2 reached end of life on May 16, 2023 and is no longer receiving security patches.
What should I upgrade to from CockroachDB 21.2?
The recommended upgrade from CockroachDB 21.2 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 21.2 past EOL?
When CockroachDB 21.2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL CockroachDB should migrate immediately or implement compensating controls.