Skip to content
statance
MenuClose
← All Jenkins releases

Is Jenkins 2.568 end of life?

Supported

No. Jenkins 2.568 is supported and no end-of-life date has been announced yet.

Released
10 June 2026
Security support ends
No date announced
Latest release
2.568.3 · 31 August 2026
Long-term support
Yes

What this means for your servers

Jenkins 2.568 is safe to run. Install updates regularly so you stay on the latest release in this cycle (2.568.3).

How to check if you’re running Jenkins 2.568

CLI

java -jar jenkins.war --version # or Manage Jenkins → About Jenkins

What to upgrade to

Jenkins 2.568 is already the newest recommended release.

Prefer the LTS line, which is updated every four weeks. Back up JENKINS_HOME, update plugins first, then the core. Jenkins exposed to the internet should be patched promptly, as security advisories are frequent.

Find end-of-life software before an auditor does

Statance tracks end-of-life status for operating systems, runtimes, databases and web servers across your fleet, and raises a finding when anything goes past end of life. Security monitoring is included in Pro and Business. How security monitoring works.

Other Jenkins releases

ReleaseStatusSecurity support ends
Jenkins 2.555End of life10 June 2026
Jenkins 2.541End of life15 April 2026
Jenkins 2.528End of life21 January 2026
Jenkins RegularSupportedNo date announced

All Jenkins end-of-life dates →

FAQ

Is Jenkins 2.568 end of life?

No. Jenkins 2.568 is supported and no end-of-life date has been announced yet.

Can I keep running Jenkins 2.568 after end of life?

It keeps working, but new vulnerabilities will not be fixed, so every newly published CVE stays open on your server. Scanners and compliance frameworks (PCI DSS, SOC 2, Cyber Essentials) treat unsupported software as a finding.

What is the latest version of Jenkins 2.568?

The latest release in this cycle is 2.568.3, released on 31 August 2026.

Lifecycle data from endoflife.date/jenkins, refreshed 17 November 2026. Vendors occasionally change dates; check the vendor’s own lifecycle page before making a compliance decision.

Stop tracking end-of-life dates by hand.

Statance flags end-of-life and vulnerable software on every server automatically.