← ← Back to all products
All badges & lifecycle API →
ClickHouseEnd of Life (EOL) Dates & Support Status
Active
OtherLatest Version: 26.9.3.38Latest Release: Sep 26, 2026
Support summary
ClickHouse currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
Mar 26, 2027
ClickHouse 26.3 · 180 days left
Supported cycles
4
4 lts
Versions
21
Latest Version
26.9.3.38
Active Support
4
EOL
17
Lifecycle Timeline
Dec 18, 2025As of Sep 27, 2026
26.9Active · Date not announced
26.8Active · Aug 27, 2027
26.7Active · Date not announced
26.6EOL · Sep 21, 2026
26.5EOL · Aug 27, 2026
26.4EOL · Jul 22, 2026
26.3Active · Mar 26, 2027
26.2EOL · May 21, 2026
26.1EOL · May 5, 2026
25.12EOL · Mar 26, 2026
ActiveSecurityEOLHistorical phase unknown
Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 26.9 | Sep 21, 2026 | Maintained | Date not announced | 26.9.3.38 | No | Active |
| 26.8 | Aug 27, 2026 | Maintained | Aug 27, 2027 | 26.8.12.53 | Yes | Active |
| 26.7 | Jul 22, 2026 | Maintained | Date not announced | 26.7.15.52 | No | Active |
| 26.6 | Jun 25, 2026 | Ended | Sep 21, 2026 | 26.6.8.7 | No | EOL |
| 26.5 | May 21, 2026 | Ended | Aug 27, 2026 | 26.5.7.64 | No | EOL |
| 26.4 | May 5, 2026 | Ended | Jul 22, 2026 | 26.4.5.143 | No | EOL |
| 26.3 | Mar 26, 2026 | Maintained | Mar 26, 2027 | 26.3.34.136 | Yes | Active |
| 26.2 | Feb 27, 2026 | Ended | May 21, 2026 | 26.2.19.43 | No | EOL |
| 26.1 | Jan 30, 2026 | Ended | May 5, 2026 | 26.1.12.23 | No | EOL |
| 25.12 | Dec 18, 2025 | Ended | Mar 26, 2026 | 25.12.12.1 | No | EOL |
| 25.11 | Nov 27, 2025 | Ended | Feb 27, 2026 | 25.11.9.34 | No | EOL |
| 25.10 | Nov 1, 2025 | Ended | Jan 30, 2026 | 25.10.7.6 | No | EOL |
| 25.9 | Sep 27, 2025 | Ended | Dec 18, 2025 | 25.9.7.56 | No | EOL |
| 25.8 | Aug 29, 2025 | Ended | Aug 29, 2026 | 25.8.33.6 | Yes | EOL |
| 25.7 | Jul 29, 2025 | Ended | Nov 1, 2025 | 25.7.8.71 | No | EOL |
| 25.6 | Jun 26, 2025 | Ended | Sep 27, 2025 | 25.6.13.41 | No | EOL |
| 25.5 | May 22, 2025 | Ended | Aug 29, 2025 | 25.5.11.15 | No | EOL |
| 25.4 | Apr 22, 2025 | Ended | Jul 29, 2025 | 25.4.13.22 | No | EOL |
| 25.3 | Mar 20, 2025 | Ended | Mar 20, 2026 | 25.3.14.14 | Yes | EOL |
| 25.2 | Feb 28, 2025 | Ended | May 22, 2025 | 25.2.2.39 | No | EOL |
| 25.1 | Jan 28, 2025 | Ended | Apr 22, 2025 | 25.1.8.25 | No | EOL |
Data sources
Embed this badge
Show ClickHouse's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.
Markdown
[](https://eol.wiki/clickhouse/)HTML
<a href="https://eol.wiki/clickhouse/"><img src="https://eol.wiki/badge/clickhouse.svg" alt="ClickHouse end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of ClickHouse have reached end of life?
The following ClickHouse versions have reached end of life and no longer receive security updates: 26.6, 26.5, 26.4, 26.2, 26.1, 25.12, 25.11, 25.10 (and 9 more). It is recommended to upgrade to a supported version.
Is it safe to continue using ClickHouse 26.6?
ClickHouse 26.6 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of ClickHouse?
The latest version of ClickHouse is 26.9.3.38, released in the 26.9 release cycle.
How many versions of ClickHouse are currently supported?
ClickHouse currently has 4 actively supported version(s): 26.9, 26.8, 26.7, 26.3.
When does ClickHouse 26.9 reach end of life?
ClickHouse 26.9 does not have a specific end-of-life date announced yet.
What should I do when ClickHouse reaches end of life?
When a ClickHouse version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.