Clickhouse End of Life Dates

other

Developers working with online analytical processing require a robust and efficient database management system to generate analytical reports in real-time. ClickHouse, an open-source column-oriented DBMS, has been meeting this need since its creation, allowing users to leverage SQL queries for instant insights. Maintained by ClickHouse Inc, this powerful tool has been a go-to solution for many, given its ability to handle large volumes of data with ease and speed. With its origins rooted in solving complex data analysis challenges, ClickHouse has evolved to become a staple in the developer community, particularly for those involved in OLAP tasks.

The end-of-life landscape for ClickHouse is characterized by a total of 17 versions, with 13 of these already reaching their end-of-life status. Currently, there are 4 active versions, ensuring that developers have multiple options for their projects. The latest stable version, 25.8.24.21, offers the most recent enhancements and security patches. Looking ahead, version 25.8 is slated to reach its end-of-life on 2026-08-29, marking an important milestone for developers who may need to plan their version upgrades or migrations. This follows the recent end-of-life date of version 26.2, which occurred on 2026-05-21, underscoring the dynamic nature of software lifecycle management.

From a security standpoint, ClickHouse presents a clean slate, with a total of 0 CVEs tracked and no critical vulnerabilities reported. This exemplary security record means that the most affected version is non-applicable, given the absence of any known vulnerabilities. With no CVEs to consider, developers can focus on leveraging ClickHouse's capabilities without the burden of known security risks. To maintain this secure posture, developers should remain vigilant and ensure they are using one of the active versions, planning for upgrades as necessary to stay ahead of impending end-of-life dates and potential future security issues.

Last updated: Oct 23, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
26.9 Sep 21, 2026—No—26.9.25.15—Active
26.8 LTSAug 27, 2026—Aug 27, 2027in 308d26.8.34.13—Active
26.7 Jul 22, 2026—No—26.7.37.6—Active
26.6 Jun 25, 2026—Sep 21, 202632d ago26.6.8.7—EOL
26.5 May 21, 2026—Aug 27, 202657d ago26.5.7.64—EOL
26.4 May 5, 2026—Jul 22, 202693d ago26.4.5.143—EOL
26.3 LTSMar 26, 2026—Mar 26, 2027in 154d26.3.59.10—Active
26.2 Feb 27, 2026—May 21, 2026155d ago26.2.19.43—EOL
26.1 Jan 30, 2026—May 5, 2026171d ago26.1.12.23—EOL
25.12 Dec 18, 2025—Mar 26, 2026211d ago25.12.12.1—EOL
25.11 Nov 27, 2025—Feb 27, 2026238d ago25.11.9.34—EOL
25.10 Nov 1, 2025—Jan 30, 2026266d ago25.10.7.6—EOL
25.9 Sep 27, 2025—Dec 18, 2025309d ago25.9.7.56—EOL
25.8 LTSAug 29, 2025—Aug 29, 202655d ago25.8.33.6—EOL
25.7 Jul 29, 2025—Nov 1, 2025356d ago25.7.8.71—EOL
25.6 Jun 26, 2025—Sep 27, 2025391d ago25.6.13.41—EOL
25.5 May 22, 2025—Aug 29, 2025420d ago25.5.11.15—EOL
25.4 Apr 22, 2025—Jul 29, 2025451d ago25.4.13.22—EOL
25.3 LTSMar 20, 2025—Mar 20, 2026217d ago25.3.14.14—EOL
25.2 Feb 28, 2025—May 22, 2025519d ago25.2.2.39—EOL
25.1 Jan 28, 2025—Apr 22, 2025549d ago25.1.8.25—EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions