Sonarqube Server · Lifecycle Status

Sonarqube Server End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Sonarqube Server versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Sonarqube Server 2026.2 reaches end of life on May 18, 2026. Plan your migration now — 9 days remaining.
Latest Active
2025.4.6
2025.4 series
Next EOL
2026.2
May 18, 2026
Active Versions
3
of 12 total
EOL Versions
7
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 2018201920202021202220232024202520262027789102025.12025.22025.32025.42025.52025.62026.12026.2TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
7 LTS 7.9.6 Feb 2, 2018 May 4, 2021 1831 days past EOL EOL
8 LTS 8.9.10 Oct 15, 2019 Feb 7, 2023 1187 days past EOL EOL
9 LTS 9.9.8 Jul 5, 2021 Jan 20, 2025 474 days past EOL EOL
10 10.8.0 Mar 30, 2023 Mar 26, 2025 409 days past EOL EOL
2025.1 LTS 2025.1.7 Jan 23, 2025 Jul 1, 2026 53 days remaining Warning
2025.2 2025.2.0 Mar 27, 2025 May 26, 2025 348 days past EOL EOL
2025.3 2025.3.1 May 30, 2025 Jul 29, 2025 284 days past EOL EOL
2025.4 LTS 2025.4.6 Jul 30, 2025 Jan 30, 2027 266 days remaining Active
2025.5 2025.5 Sep 26, 2025 Dec 12, 2025 148 days past EOL EOL
2025.6 2025.6.1 Dec 12, 2025 Already EOL Supported Active
2026.1 LTS 2026.1.2 Jan 30, 2026 Aug 2, 2027 450 days remaining Active
2026.2 2026.2.1 Mar 24, 2026 May 18, 2026 9 days remaining Warning

What does Sonarqube Server end of life mean for your organization?

When a Sonarqube Server version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.

Organizations running EOL Sonarqube Server should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Sonarqube Server?
The next Sonarqube Server version reaching EOL is 2026.2 on May 18, 2026. See the full table above for all version EOL dates.
What is the latest supported version of Sonarqube Server?
The latest active version of Sonarqube Server is 2025.4.6. Always verify against the table above as support windows can change.
What happens when Sonarqube Server reaches end of life?
When Sonarqube Server reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Sonarqube Server?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Sonarqube Server versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →