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 from endoflife.date and official vendor documentation.
⚠
Jenkins 2.387 is past end of life. This version no longer receives security patches. 1074 days past EOL — migrate to a supported version immediately.
EOL Date
May 31, 2023
1074 days past EOL
Latest Release
2.387.3
LTS release
Release Date
Jan 17, 2023
Jenkins 2.387 series
| 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 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Jenkins 2.387 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Jenkins 2.541 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.541 — 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 remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Jenkins should migrate immediately or implement compensating controls.