Jenkins End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Jenkins versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.346 LTS | 2.346.3 | May 3, 2022 | Sep 7, 2022 | 1432 days past EOL | EOL |
| 2.361 LTS | 2.361.4 | Jul 26, 2022 | Nov 30, 2022 | 1348 days past EOL | EOL |
| 2.375 LTS | 2.375.4 | Oct 25, 2022 | Mar 8, 2023 | 1250 days past EOL | EOL |
| 2.387 LTS | 2.387.3 | Jan 17, 2023 | May 31, 2023 | 1166 days past EOL | EOL |
| 2.401 LTS | 2.401.3 | Apr 18, 2023 | Aug 23, 2023 | 1082 days past EOL | EOL |
| 2.414 LTS | 2.414.3 | Jul 11, 2023 | Nov 15, 2023 | 998 days past EOL | EOL |
| 2.426 LTS | 2.426.3 | Oct 3, 2023 | Feb 21, 2024 | 900 days past EOL | EOL |
| 2.440 LTS | 2.440.3 | Jan 10, 2024 | May 15, 2024 | 816 days past EOL | EOL |
| 2.452 LTS | 2.452.4 | Apr 2, 2024 | Aug 7, 2024 | 732 days past EOL | EOL |
| 2.462 LTS | 2.462.3 | Jun 10, 2024 | Oct 2, 2024 | 676 days past EOL | EOL |
| 2.479 LTS | 2.479.3 | Sep 27, 2024 | Feb 5, 2025 | 550 days past EOL | EOL |
| 2.492 LTS | 2.492.3 | Jan 7, 2025 | Apr 30, 2025 | 466 days past EOL | EOL |
| 2.504 LTS | 2.504.3 | Mar 31, 2025 | Jul 23, 2025 | 382 days past EOL | EOL |
| 2.516 LTS | 2.516.3 | Jun 24, 2025 | Oct 15, 2025 | 298 days past EOL | EOL |
| 2.528 LTS | 2.528.3 | Sep 17, 2025 | Jan 21, 2026 | 200 days past EOL | EOL |
| 2.541 LTS | 2.541.3 | Dec 10, 2025 | Apr 15, 2026 | 116 days past EOL | EOL |
| 2.555 LTS | 2.555.3 | Mar 18, 2026 | Jul 9, 2026 | 31 days past EOL | EOL |
| 2.568 LTS | 2.568.2 | Jun 10, 2026 | TBD | Supported | Active |
| Regular | 2.576 | Apr 20, 2016 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/jenkins)
What does Jenkins end of life mean for your organization?
When a version of Jenkins reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Jenkins should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Jenkins reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Jenkins versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Jenkins has 17 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Jenkins exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.