Jenkins 2.387 · Version Status

Jenkins 2.387 End of Life Date

Jenkins 2.387 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.387 is past end of life. This version no longer receives security patches. 1235 days past EOL — migrate to a supported version immediately.
EOL Date
May 31, 2023
1235 days past EOL
Latest Release
2.387.3
LTS release
Release Date
Jan 17, 2023
Jenkins 2.387 series
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Lifecycle detail

Jenkins 2.387 was released on January 17, 2023 and support ended on May 31, 2023 — a supported lifespan of 4 months, in line with the 4 months median for Jenkins LTS releases. It was a long-term support (LTS) release, so it received a longer patch window than the interim releases around it. The last patch it will ever receive is 2.387.3, published May 3, 2023 — 28 days before support ended. It has been without security patches for 3 years and 5 months. 14 newer Jenkins releases have shipped since.

← Jenkins 2.375 All Jenkins versions Jenkins 2.401 →
80 / 100
Critical Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
40/40
Attack Surface
20/30 High tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
Recommended upgrade path
Jenkins 2.580
Latest release: 2.580.1 · EOL: Supported
View full Jenkins timeline →
Extended Support
Extended Jenkins 2.387 support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
All Jenkins Versions
VersionLatestEOL DateStatus
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 2.387 end of life mean?

When Jenkins 2.387 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 2.387 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to Jenkins 2.580 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Jenkins 2.387 reach end of life?
Jenkins 2.387 reached end of life on May 31, 2023. This version is no longer receiving security patches.
Is Jenkins 2.387 still supported?
No. Jenkins 2.387 reached end of life on May 31, 2023 and is no longer receiving security patches.
What should I upgrade to from Jenkins 2.387?
The recommended upgrade from Jenkins 2.387 is Jenkins 2.580 — the latest actively supported version. Check the Jenkins full timeline for all supported versions.
What are the security risks of running Jenkins 2.387 past EOL?
When Jenkins 2.387 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Jenkins should migrate immediately or implement compensating controls.
Deep Dive
Full guide
Every Jenkins LTS Except the Newest Is Now Permanently Vulnerable — CVE-2026-70426
→
Data from endoflife.date API · Generated at build time · How we source data →
Related Products
KubernetesJavaNode.jsPython