Jenkins End of Life (EOL) Dates & Support Timeline

Jenkins release and support pattern

Across the 20 release lines with a published release date, Jenkins has shipped a new line roughly every 3 months (median interval). A line typically stays supported for about 4 months from its release to its end-of-life date (measured on the 18 lines with both dates published). 19 of the 20 tracked lines are designated long-term support, which is where the longer windows sit.

Of the 20 release lines tracked, 18 are past end of life and 2 are still within support. The newest line, 2.580, was released September 2, 2026. No end-of-life date is currently published for the 2 supported lines.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

Jenkins security intelligence

CISA KEV history: Jenkins is named in CISA's Known Exploited Vulnerabilities catalog 6 times, most recently on 2025-10-02, including use in ransomware campaigns. Derived from CISA's live catalog at every build.

Patch behavior after end of life: Hard cutoff — supported versions only. Jenkins fixes security issues in the current weekly and current LTS lines; older LTS lines age out quickly and are listed as affected without receiving fixes (CVE-2026-70426 affects EOL LTS 2.492–2.555, fixed only in 2.568.2). The project's LTS cadence makes the cutoff predictable and fast. (Observed behavior from our primary-source verification sweep, checked 2026-08-07 — never a guarantee of future fixes.)

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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps 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.

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.

Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.

Extended Support Options

If you cannot migrate immediately, check whether the vendor or a third party sells extended support with security patches for your Jenkins version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.

Related Products