Jenkins · Lifecycle Status

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.

Jenkins 2.541.3 is actively supported. No versions approaching EOL in the next 6 months.
Latest Active
2.541.3
2.541 series
Next EOL
None upcoming
Active Versions
2
of 17 total
EOL Versions
15
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 201720182019202020212022202320242025202622.3462.3612.3752.3872.4012.4142.4262.4402.4522.4622.4792.4922.5042.5162.5282.541TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
2.346 LTS 2.346.3 May 3, 2022 Sep 7, 2022 1340 days past EOL EOL
2.361 LTS 2.361.4 Jul 26, 2022 Nov 30, 2022 1256 days past EOL EOL
2.375 LTS 2.375.4 Oct 25, 2022 Mar 8, 2023 1158 days past EOL EOL
2.387 LTS 2.387.3 Jan 17, 2023 May 31, 2023 1074 days past EOL EOL
2.401 LTS 2.401.3 Apr 18, 2023 Aug 23, 2023 990 days past EOL EOL
2.414 LTS 2.414.3 Jul 11, 2023 Nov 15, 2023 906 days past EOL EOL
2.426 LTS 2.426.3 Oct 3, 2023 Feb 21, 2024 808 days past EOL EOL
2.440 LTS 2.440.3 Jan 10, 2024 May 15, 2024 724 days past EOL EOL
2.452 LTS 2.452.4 Apr 2, 2024 Aug 7, 2024 640 days past EOL EOL
2.462 LTS 2.462.3 Jun 10, 2024 Oct 2, 2024 584 days past EOL EOL
2.479 LTS 2.479.3 Sep 27, 2024 Feb 5, 2025 458 days past EOL EOL
2.492 LTS 2.492.3 Jan 7, 2025 Apr 30, 2025 374 days past EOL EOL
2.504 LTS 2.504.3 Mar 31, 2025 Jul 23, 2025 290 days past EOL EOL
2.516 LTS 2.516.3 Jun 24, 2025 Oct 15, 2025 206 days past EOL EOL
2.528 LTS 2.528.3 Sep 17, 2025 Jan 21, 2026 108 days past EOL EOL
2.541 LTS 2.541.3 Dec 10, 2025 Already EOL Supported Active
2 2.563 Apr 20, 2016 Already EOL Supported Active

What does Jenkins end of life mean for your organization?

When a Jenkins version 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.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Jenkins?
See the full table above for all Jenkins version EOL dates.
What is the latest supported version of Jenkins?
The latest active version of Jenkins is 2.541.3. Always verify against the table above as support windows can change.
What happens when Jenkins reaches end of life?
When Jenkins reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Jenkins?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Jenkins versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →