ClickHouse End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all ClickHouse versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 25.1 | 25.1.8.25 | Jan 28, 2025 | Apr 22, 2025 | 427 days past EOL | EOL |
| 25.2 | 25.2.2.39 | Feb 28, 2025 | May 22, 2025 | 397 days past EOL | EOL |
| 25.3 LTS | 25.3.14.14 | Mar 20, 2025 | Mar 20, 2026 | 95 days past EOL | EOL |
| 25.4 | 25.4.13.22 | Apr 22, 2025 | Jul 29, 2025 | 329 days past EOL | EOL |
| 25.5 | 25.5.11.15 | May 22, 2025 | Aug 29, 2025 | 298 days past EOL | EOL |
| 25.6 | 25.6.13.41 | Jun 26, 2025 | Sep 27, 2025 | 269 days past EOL | EOL |
| 25.7 | 25.7.8.71 | Jul 29, 2025 | Nov 1, 2025 | 234 days past EOL | EOL |
| 25.8 LTS | 25.8.24.21 | Aug 29, 2025 | Aug 29, 2026 | 67 days remaining | Warning |
| 25.9 | 25.9.7.56 | Sep 27, 2025 | Dec 18, 2025 | 187 days past EOL | EOL |
| 25.10 | 25.10.7.6 | Nov 1, 2025 | Jan 30, 2026 | 144 days past EOL | EOL |
| 25.11 | 25.11.9.34 | Nov 27, 2025 | Feb 27, 2026 | 116 days past EOL | EOL |
| 25.12 | 25.12.12.1 | Dec 18, 2025 | Mar 26, 2026 | 89 days past EOL | EOL |
| 26.1 | 26.1.12.23 | Jan 30, 2026 | May 5, 2026 | 49 days past EOL | EOL |
| 26.2 | 26.2.19.43 | Feb 27, 2026 | May 21, 2026 | 33 days past EOL | EOL |
| 26.3 LTS | 26.3.14.49 | Mar 26, 2026 | Mar 26, 2027 | 276 days remaining | Active |
| 26.4 | 26.4.4.38 | May 5, 2026 | TBD | Supported | Active |
| 26.5 | 26.5.3.52 | May 21, 2026 | TBD | Supported | Active |
What does ClickHouse end of life mean for your organization?
When a version of ClickHouse reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL ClickHouse should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL ClickHouse versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →