← ← Back to all products
All badges & lifecycle API →
SonarQube ServerEnd of Life (EOL) Dates & Support Status
Active
Tools & MonitoringLatest Version: 2026.1.6Latest Release: Sep 23, 2026
SonarQube Server is the enterprise edition of SonarQube with advanced code analysis and governance features.
Support summary
SonarQube Server has cycles in security-only maintenance. Production workloads should move toward actively supported releases.
What do EOL and support statuses mean?Next EOL
Jan 30, 2027
SonarQube Server 2025.4 · 125 days left
Supported cycles
3
6 lts
Versions
14
Latest Version
2026.1.6
Active Support
2
EOL
11
Lifecycle Timeline
Jan 23, 2025As of Sep 27, 2026
2026.4Active · Date not announced
2026.3EOL · Jul 23, 2026
2026.2EOL · May 21, 2026
2026.1Active · Aug 2, 2027
2025.6EOL · Jan 30, 2026
2025.5EOL · Dec 12, 2025
2025.4Security · Jan 30, 2027
2025.3EOL · Jul 29, 2025
2025.2EOL · May 26, 2025
2025.1EOL · Jul 1, 2026
ActiveSecurityEOLHistorical phase unknown
Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 2026.4 | Jul 23, 2026 | Maintained | Date not announced | 2026.4.1 | No | Active |
| 2026.3 | May 21, 2026 | Jul 23, 2026 | Jul 23, 2026 | 2026.3.1 | No | EOL |
| 2026.2 | Mar 24, 2026 | May 21, 2026 | May 21, 2026 | 2026.2.1 | No | EOL |
| 2026.1 | Jan 30, 2026 | Jan 30, 2027 | Aug 2, 2027 | 2026.1.6 | Yes | Active |
| 2025.6 | Dec 12, 2025 | Jan 30, 2026 | Jan 30, 2026 | 2025.6.1 | No | EOL |
| 2025.5 | Sep 26, 2025 | Dec 12, 2025 | Dec 12, 2025 | 2025.5 | No | EOL |
| 2025.4 | Jul 30, 2025 | Jul 30, 2026 | Jan 30, 2027 | 2025.4.9 | Yes | Security |
| 2025.3 | May 30, 2025 | Jul 29, 2025 | Jul 29, 2025 | 2025.3.1 | No | EOL |
| 2025.2 | Mar 27, 2025 | May 26, 2025 | May 26, 2025 | 2025.2.0 | No | EOL |
| 2025.1 | Jan 23, 2025 | Jan 23, 2026 | Jul 1, 2026 | 2025.1.8 | Yes | EOL |
| 10 | Mar 30, 2023 | Jan 20, 2025 | Mar 26, 2025 | 10.8.0 | No | EOL |
| 9 | Jul 5, 2021 | Mar 30, 2023 | Jan 20, 2025 | 9.9.8 | 2023-02-07 | EOL |
| 8 | Oct 15, 2019 | Jul 5, 2021 | Feb 7, 2023 | 8.9.10 | 2021-05-04 | EOL |
| 7 | Feb 2, 2018 | Oct 16, 2019 | May 4, 2021 | 7.9.6 | 2019-07-01 | EOL |
Data sources
Embed this badge
Show SonarQube Server's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.
Markdown
[](https://eol.wiki/sonarqube-server/)HTML
<a href="https://eol.wiki/sonarqube-server/"><img src="https://eol.wiki/badge/sonarqube-server.svg" alt="SonarQube Server end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of SonarQube Server have reached end of life?
The following SonarQube Server versions have reached end of life and no longer receive security updates: 2026.3, 2026.2, 2025.6, 2025.5, 2025.3, 2025.2, 2025.1, 10 (and 3 more). It is recommended to upgrade to a supported version.
Is it safe to continue using SonarQube Server 2026.3?
SonarQube Server 2026.3 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of SonarQube Server?
The latest version of SonarQube Server is 2026.1.6, released in the 2026.1 release cycle.
How many versions of SonarQube Server are currently supported?
SonarQube Server currently has 3 actively supported version(s): 2026.4, 2026.1, 2025.4.
When does SonarQube Server 2026.4 reach end of life?
SonarQube Server 2026.4 does not have a specific end-of-life date announced yet.
What should I do when SonarQube Server reaches end of life?
When a SonarQube Server version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.