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
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 2026.3 | May 21, 2026 | Jul 20, 2026 | Jul 20, 2026 | 4d ago | 2026.3.1 | — | EOL | |
| 2026.2 | Mar 24, 2026 | May 18, 2026 | May 18, 2026 | 67d ago | 2026.2.1 | — | EOL | |
| 2026.1 LTS | Jan 30, 2026 | Jan 30, 2027 | Aug 2, 2027 | in 374d | 2026.1.3 | — | Active | |
| 2025.6 | Dec 12, 2025 | — | No | — | 2025.6.1 | — | Active | |
| 2025.5 | Sep 26, 2025 | Dec 12, 2025 | Dec 12, 2025 | 224d ago | 2025.5 | — | EOL | |
| 2025.4 LTS | Jul 30, 2025 | Jul 30, 2026 | Jan 30, 2027 | in 190d | 2025.4.7 | — | Active | |
| 2025.3 | May 30, 2025 | Jul 29, 2025 | Jul 29, 2025 | 360d ago | 2025.3.1 | — | EOL | |
| 2025.2 | Mar 27, 2025 | May 26, 2025 | May 26, 2025 | 424d ago | 2025.2.0 | — | EOL | |
| 2025.1 LTS | Jan 23, 2025 | Jan 23, 2026 | Jul 1, 2026 | 23d ago | 2025.1.8 | — | EOL | |
| 10 | Mar 30, 2023 | Jan 20, 2025 | Mar 26, 2025 | 485d ago | 10.8.0 | — | EOL | |
| 9 LTS | Jul 5, 2021 | Mar 30, 2023 | Jan 20, 2025 | 550d ago | 9.9.8 | — | EOL | |
| 8 LTS | Oct 15, 2019 | Jul 5, 2021 | Feb 7, 2023 | 1263d ago | 8.9.10 | — | EOL | |
| 7 LTS | Feb 2, 2018 | Oct 16, 2019 | May 4, 2021 | 1907d ago | 7.9.6 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
