Jenkins 2.528 End of Life Date
Jenkins 2.528 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.
Jenkins 2.528 was released on September 17, 2025 and support ended on January 21, 2026 — a supported lifespan of 4 months, in line with the 4 months median for Jenkins 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 2.528.3, published December 8, 2025 — 44 days before support ended. It has been without security patches for 8 months. 2 newer Jenkins releases have shipped since.
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →| Version | Latest | EOL Date | Status |
|---|---|---|---|
| 2.346 LTS | 2.346.3 | Sep 7, 2022 | EOL |
| 2.361 LTS | 2.361.4 | Nov 30, 2022 | EOL |
| 2.375 LTS | 2.375.4 | Mar 8, 2023 | EOL |
| 2.387 LTS | 2.387.3 | May 31, 2023 | EOL |
| 2.401 LTS | 2.401.3 | Aug 23, 2023 | EOL |
| 2.414 LTS | 2.414.3 | Nov 15, 2023 | EOL |
| 2.426 LTS | 2.426.3 | Feb 21, 2024 | EOL |
| 2.440 LTS | 2.440.3 | May 15, 2024 | EOL |
What does Jenkins 2.528 end of life mean?
When Jenkins 2.528 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 Jenkins 2.528 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Jenkins 2.568 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.