Sonarqube Server End of Life Dates

other

Developers rely on the Sonarqube Server to track and manage their code quality, and staying on top of its end-of-life dates is crucial for maintaining security and compliance. The Sonarqube Server was first introduced to help teams identify and fix issues in their codebases, and it has been maintained by SonarSource since its inception. With a history of providing valuable insights into code health, the Sonarqube Server has become an essential tool for many development teams, allowing them to prioritize and address potential problems before they become major issues.

The Sonarqube Server has a total of 13 versions, with 8 of these versions having already reached their end-of-life. Currently, 5 versions remain active and supported, with the latest stable version being 2025.1.8. Looking ahead, the next version slated to reach its end-of-life is 2025.1, which will occur on 2026-07-01. This means that any teams still relying on this version will need to plan their upgrades before this date to ensure continued support and security. The most recent version to reach its end-of-life was 2026.2, which occurred on 2026-05-18, highlighting the importance of staying up-to-date with the latest version releases.

From a security perspective, the Sonarqube Server has a clean track record, with a total of 0 CVEs tracked and 0 critical CVEs. As a result, there is no most affected version, and the KEV status is not applicable. This lack of security vulnerabilities is a testament to the robustness of the Sonarqube Server, but it does not eliminate the need for developers to stay vigilant and ensure they are running supported versions. To maintain the security and integrity of their codebases, developers should continue to monitor the Sonarqube Server's end-of-life dates and plan their upgrades accordingly, taking advantage of the latest features and security patches to minimize potential risks.

Last updated: Jul 24, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
2026.3 May 21, 2026Jul 20, 2026Jul 20, 20264d ago2026.3.1EOL
2026.2 Mar 24, 2026May 18, 2026May 18, 202667d ago2026.2.1EOL
2026.1 LTSJan 30, 2026Jan 30, 2027Aug 2, 2027in 374d2026.1.3Active
2025.6 Dec 12, 2025No2025.6.1Active
2025.5 Sep 26, 2025Dec 12, 2025Dec 12, 2025224d ago2025.5EOL
2025.4 LTSJul 30, 2025Jul 30, 2026Jan 30, 2027in 190d2025.4.7Active
2025.3 May 30, 2025Jul 29, 2025Jul 29, 2025360d ago2025.3.1EOL
2025.2 Mar 27, 2025May 26, 2025May 26, 2025424d ago2025.2.0EOL
2025.1 LTSJan 23, 2025Jan 23, 2026Jul 1, 202623d ago2025.1.8EOL
10 Mar 30, 2023Jan 20, 2025Mar 26, 2025485d ago10.8.0EOL
9 LTSJul 5, 2021Mar 30, 2023Jan 20, 2025550d ago9.9.8EOL
8 LTSOct 15, 2019Jul 5, 2021Feb 7, 20231263d ago8.9.10EOL
7 LTSFeb 2, 2018Oct 16, 2019May 4, 20211907d ago7.9.6EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions