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.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 7 LTS | 7.9.6 | Feb 2, 2018 | May 4, 2021 | 1876 days past EOL | EOL |
| 8 LTS | 8.9.10 | Oct 15, 2019 | Feb 7, 2023 | 1232 days past EOL | EOL |
| 9 LTS | 9.9.8 | Jul 5, 2021 | Jan 20, 2025 | 519 days past EOL | EOL |
| 10 | 10.8.0 | Mar 30, 2023 | Mar 26, 2025 | 454 days past EOL | EOL |
| 2025.1 LTS | 2025.1.8 | Jan 23, 2025 | Jul 1, 2026 | 8 days remaining | Warning |
| 2025.2 | 2025.2.0 | Mar 27, 2025 | May 26, 2025 | 393 days past EOL | EOL |
| 2025.3 | 2025.3.1 | May 30, 2025 | Jul 29, 2025 | 329 days past EOL | EOL |
| 2025.4 LTS | 2025.4.7 | Jul 30, 2025 | Jan 30, 2027 | 221 days remaining | Active |
| 2025.5 | 2025.5 | Sep 26, 2025 | Dec 12, 2025 | 193 days past EOL | EOL |
| 2025.6 | 2025.6.1 | Dec 12, 2025 | TBD | Supported | Active |
| 2026.1 LTS | 2026.1.3 | Jan 30, 2026 | Aug 2, 2027 | 405 days remaining | Active |
| 2026.2 | 2026.2.1 | Mar 24, 2026 | May 18, 2026 | 36 days past EOL | EOL |
| 2026.3 | 2026.3.1 | May 21, 2026 | Jul 20, 2026 | 27 days remaining | Warning |
What does SonarQube Server end of life mean for your organization?
When a version of SonarQube Server 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL SonarQube Server versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →