SonarQube Server 2026.5 · Version Status

SonarQube Server 2026.5 End of Life Date

SonarQube Server 2026.5 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

✓ SonarQube Server 2026.5 is actively supported. EOL date: March 1, 2028.
📅 Get reminded before SonarQube Server 2026.5 reaches EOL on March 1, 2028 — alerts 90, 30 & 7 days out.
Google →
✉️ Or get it by email — alerts at 90 / 60 / 30 / 7 days and on the day: Free · one-click unsubscribe in every email · no other mail, ever
EOL Date
Mar 1, 2028
518 days remaining
Latest Release
2026.5.0
LTS release
Release Date
Sep 29, 2026
SonarQube Server 2026.5 series
Lifecycle detail

SonarQube Server 2026.5 was released on September 29, 2026 and support is scheduled to end on March 1, 2028 — a planned supported lifespan of 1 year and 5 months, in line with the 1 year and 6 months median for SonarQube Server LTS releases. It is a long-term support (LTS) release, so it carries a longer patch window than the interim releases around it. Its most recent patch is 2026.5.0, published September 29, 2026.

← SonarQube Server 2026.4 All SonarQube Server versions
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
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 →
All SonarQube Server Versions
VersionLatestEOL DateStatus
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.9 Jan 30, 2027 Warning

What does SonarQube Server 2026.5 end of life mean?

When SonarQube Server 2026.5 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running SonarQube Server 2026.5 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to SonarQube Server 2026.5 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does SonarQube Server 2026.5 reach end of life?
SonarQube Server 2026.5 reached end of life on March 1, 2028. That is 518 days remaining.
Is SonarQube Server 2026.5 still supported?
Yes, SonarQube Server 2026.5 is currently supported. The EOL date is March 1, 2028.
What should I upgrade to from SonarQube Server 2026.5?
The recommended upgrade from SonarQube Server 2026.5 is SonarQube Server 2026.5 — the latest actively supported version. Check the SonarQube Server full timeline for all supported versions.
What are the security risks of running SonarQube Server 2026.5 past EOL?
When SonarQube Server 2026.5 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL SonarQube Server should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →