CockroachDB 25.3 · Version Status
CockroachDB 25.3 End of Life Date
CockroachDB 25.3 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 25.3 is past end of life. This version no longer receives security patches. 220 days past EOL — migrate to a supported version immediately.
EOL Date
Feb 4, 2026
220 days past EOL
Latest Release
25.3.7
Standard release
Release Date
Aug 4, 2025
CockroachDB 25.3 series
Lifecycle detail
CockroachDB 25.3 was released on August 4, 2025 and support ended on February 4, 2026 — a supported lifespan of 6 months, shorter than 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 25.3.7, published January 7, 2026 — 28 days before support ended. It has been without security patches for 7 months. 2 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 25.3 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 25.3 end of life mean?
When CockroachDB 25.3 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 25.3 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 25.3 reach end of life?
CockroachDB 25.3 reached end of life on February 4, 2026. This version is no longer receiving security patches.
Is CockroachDB 25.3 still supported?
No. CockroachDB 25.3 reached end of life on February 4, 2026 and is no longer receiving security patches.
What should I upgrade to from CockroachDB 25.3?
The recommended upgrade from CockroachDB 25.3 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 25.3 past EOL?
When CockroachDB 25.3 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.