Jenkins Regular End of Life Date
Jenkins Regular 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 was released on April 20, 2016 and has no published end-of-life date yet. It is not an LTS release; Jenkins reserves longer patch windows for its LTS versions. Its most recent patch is 2.583, published September 22, 2026.
| 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 Regular end of life mean?
When Jenkins Regular 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 Jenkins Regular past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Jenkins 2.568 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.