SonarQube Community 25 · Version Status
SonarQube Community 25 End of Life Date
SonarQube Community 25 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 Community 25 is past end of life. This version no longer receives security patches. 305 days past EOL — migrate to a supported version immediately.
EOL Date
Jan 6, 2026
305 days past EOL
Latest Release
25.12.0.117093
Standard release
Release Date
Jan 7, 2025
SonarQube Community 25 series
Where these dates come from
End of lifeJan 6, 2026endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseJan 7, 2025endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
SonarQube Community 25 was released on January 7, 2025 and support ended on January 6, 2026 — a supported lifespan of 1 year, longer than the 38 days median for SonarQube Community releases. Its latest release on record is 25.12.0.117093, published December 23, 2025 — 14 days before support ended. It has been past its end-of-life date for 10 months. 10 newer SonarQube Community releases have 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 Community 25 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
All SonarQube Community Versions
| Version | Latest | EOL Date | Status |
|---|
| 7 |
7.9.6 |
May 4, 2021 |
EOL |
| 8 |
8.9.10.61524 |
Feb 7, 2023 |
EOL |
| 9 |
9.9.8.100196 |
Jan 20, 2025 |
EOL |
| 10 |
10.7.0.96327 |
Dec 2, 2024 |
EOL |
| 24 |
24.12.0.100206 |
Jan 7, 2025 |
EOL |
| → 25 |
25.12.0.117093 |
Jan 6, 2026 |
EOL |
| 26.1 |
26.1.0.118079 |
Feb 4, 2026 |
EOL |
| 26.2 |
26.2.0.119303 |
Mar 3, 2026 |
EOL |
What does SonarQube Community 25 end of life mean?
When SonarQube Community 25 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 Community 25 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to SonarQube Community 26.11 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does SonarQube Community 25 reach end of life?
SonarQube Community 25 reached end of life on January 6, 2026. This version is no longer receiving security patches.
Is SonarQube Community 25 still supported?
No. SonarQube Community 25 reached end of life on January 6, 2026 and is no longer receiving security patches.
What should I upgrade to from SonarQube Community 25?
The recommended upgrade from SonarQube Community 25 is
SonarQube Community 26.11 — the latest actively supported version. Check the
SonarQube Community full timeline for all supported versions.
What are the security risks of running SonarQube Community 25 past EOL?
Since SonarQube Community 25 reached end of life, the maintainers no longer issue 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 Community should migrate immediately or implement compensating controls.