SonarQube Server 2025.1 · Version Status
SonarQube Server 2025.1 End of Life Date
SonarQube Server 2025.1 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
SonarQube Server 2025.1 is past end of life. This version no longer receives security patches. 42 days past EOL — migrate to a supported version immediately.
EOL Date
Jul 1, 2026
42 days past EOL
Latest Release
2025.1.8
LTS release
Release Date
Jan 23, 2025
SonarQube Server 2025.1 series
Lifecycle detail
SonarQube Server 2025.1 was released on January 23, 2025 and support ended on July 1, 2026 — a supported lifespan of 1 year and 5 months, shorter than the 3 years and 3 months median for SonarQube Server LTS releases. It was a long-term support (LTS) release, so it received a longer patch window than the interim releases around it. The last patch it will ever receive is 2025.1.8, published May 29, 2026 — 33 days before support ended. It has been without security patches for 42 days. 1 newer SonarQube Server release has shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended SonarQube Server 2025.1 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All SonarQube Server Versions
| Version | Latest | EOL Date | Status |
|---|
| 7 LTS |
7.9.6 |
May 4, 2021 |
EOL |
| 8 LTS |
8.9.10 |
Feb 7, 2023 |
EOL |
| 9 LTS |
9.9.8 |
Jan 20, 2025 |
EOL |
| 10 |
10.8.0 |
Mar 26, 2025 |
EOL |
| → 2025.1 LTS |
2025.1.8 |
Jul 1, 2026 |
EOL |
| 2025.2 |
2025.2.0 |
May 26, 2025 |
EOL |
| 2025.3 |
2025.3.1 |
Jul 29, 2025 |
EOL |
| 2025.4 LTS |
2025.4.8 |
Jan 30, 2027 |
Warning |
What does SonarQube Server 2025.1 end of life mean?
When SonarQube Server 2025.1 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running SonarQube Server 2025.1 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to SonarQube Server 2026.4 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does SonarQube Server 2025.1 reach end of life?
SonarQube Server 2025.1 reached end of life on July 1, 2026. This version is no longer receiving security patches.
Is SonarQube Server 2025.1 still supported?
No. SonarQube Server 2025.1 reached end of life on July 1, 2026 and is no longer receiving security patches.
What should I upgrade to from SonarQube Server 2025.1?
The recommended upgrade from SonarQube Server 2025.1 is
SonarQube Server 2026.4 — the latest actively supported version. Check the
SonarQube Server full timeline for all supported versions.
What are the security risks of running SonarQube Server 2025.1 past EOL?
When SonarQube Server 2025.1 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL SonarQube Server should migrate immediately or implement compensating controls.