Sonarqube Community End of Life Dates

other

Developers rely on Sonarqube Community to track end-of-life dates, supported versions, and security patch timelines for their applications. Created to provide insights into code quality and security, Sonarqube Community has been a valuable tool for those looking to identify and remediate vulnerabilities. The community-driven project has been maintained by a dedicated team, who continuously work to improve its capabilities and provide support for its users. With its ability to provide detailed analytics and recommendations, Sonarqube Community has become an essential component in the development workflow of many organizations.

The end-of-life landscape for Sonarqube Community is relatively straightforward, with a total of 7 versions, 6 of which have already reached their end-of-life. The latest stable version, 26.6.0.123539, is the only active version currently supported. Notably, the last version to reach end-of-life was version 25, which occurred on 2026-01-06. Since there is no next scheduled end-of-life date, developers can continue to use the latest version without immediate concerns about support expiration. This stability allows developers to focus on their projects, knowing that their tools are up-to-date and secure.

From a security perspective, Sonarqube Community has a clean record, with 0 tracked CVEs and 0 critical vulnerabilities. As a result, there is no most affected version, and no known exploits have been reported. This pristine security posture is a testament to the dedication of the maintainers and the community surrounding the project. Given this information, developers can confidently continue to use Sonarqube Community, knowing that their applications are secure and that they will receive support for any issues that may arise. With no immediate security concerns, the focus can remain on leveraging Sonarqube Community to improve code quality and maintain the highest standards of security.

Last updated: Oct 23, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
26.10 Oct 12, 2026—No—26.10.0.133078—Active
26.9 Sep 2, 2026—Oct 12, 202611d ago26.9.0.129388—EOL
26.8 Aug 5, 2026—Sep 2, 202651d ago26.8.0.126808—EOL
26.7 Jul 8, 2026—Aug 5, 202679d ago26.7.0.124771—EOL
26.6 Jun 3, 2026—Jul 8, 2026107d ago26.6.0.123539—EOL
26.5 May 19, 2026—Jun 3, 2026142d ago26.5.0.122743—EOL
26.4 Apr 10, 2026—May 19, 2026157d ago26.4.0.121862—EOL
26.3 Mar 3, 2026—Apr 10, 2026196d ago26.3.0.120487—EOL
26.2 Feb 4, 2026—Mar 3, 2026234d ago26.2.0.119303—EOL
26 Jan 6, 2026—No—26.8.0.126808—Active
26.1 Jan 6, 2026—Feb 4, 2026261d ago26.1.0.118079—EOL
25 Jan 7, 2025—Jan 6, 2026290d ago25.12.0.117093—EOL
24 Dec 2, 2024—Jan 7, 2025654d ago24.12.0.100206—EOL
10 Mar 30, 2023—Dec 2, 2024690d ago10.7.0.96327—EOL
9 Jul 5, 2021—Jan 20, 2025641d ago9.9.8.100196—EOL
8 Oct 15, 2019—Feb 7, 20231354d ago8.9.10.61524—EOL
7 Feb 2, 2018—May 4, 20211998d ago7.9.6—EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions