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.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.346 LTS | 2.346.3 | May 3, 2022 | Sep 7, 2022 | 1385 days past EOL | EOL |
| 2.361 LTS | 2.361.4 | Jul 26, 2022 | Nov 30, 2022 | 1301 days past EOL | EOL |
| 2.375 LTS | 2.375.4 | Oct 25, 2022 | Mar 8, 2023 | 1203 days past EOL | EOL |
| 2.387 LTS | 2.387.3 | Jan 17, 2023 | May 31, 2023 | 1119 days past EOL | EOL |
| 2.401 LTS | 2.401.3 | Apr 18, 2023 | Aug 23, 2023 | 1035 days past EOL | EOL |
| 2.414 LTS | 2.414.3 | Jul 11, 2023 | Nov 15, 2023 | 951 days past EOL | EOL |
| 2.426 LTS | 2.426.3 | Oct 3, 2023 | Feb 21, 2024 | 853 days past EOL | EOL |
| 2.440 LTS | 2.440.3 | Jan 10, 2024 | May 15, 2024 | 769 days past EOL | EOL |
| 2.452 LTS | 2.452.4 | Apr 2, 2024 | Aug 7, 2024 | 685 days past EOL | EOL |
| 2.462 LTS | 2.462.3 | Jun 10, 2024 | Oct 2, 2024 | 629 days past EOL | EOL |
| 2.479 LTS | 2.479.3 | Sep 27, 2024 | Feb 5, 2025 | 503 days past EOL | EOL |
| 2.492 LTS | 2.492.3 | Jan 7, 2025 | Apr 30, 2025 | 419 days past EOL | EOL |
| 2.504 LTS | 2.504.3 | Mar 31, 2025 | Jul 23, 2025 | 335 days past EOL | EOL |
| 2.516 LTS | 2.516.3 | Jun 24, 2025 | Oct 15, 2025 | 251 days past EOL | EOL |
| 2.528 LTS | 2.528.3 | Sep 17, 2025 | Jan 21, 2026 | 153 days past EOL | EOL |
| 2.541 LTS | 2.541.3 | Dec 10, 2025 | TBD | Supported | Active |
| 2 | 2.569 | Apr 20, 2016 | TBD | Supported | Active |
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.
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.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →