Eclipse Jetty 8 · Version Status
Eclipse Jetty 8 End of Life Date
Eclipse Jetty 8 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.
⚠
Eclipse Jetty 8 is past end of life. This version no longer receives security patches. Past EOL — migrate to a supported version immediately.
EOL Date
date not published
Past EOL
Latest Release
8.2.0.v20160908
Standard release
Release Date
Sep 1, 2011
Eclipse Jetty 8 series
Where these dates come from
ReleaseSep 1, 2011endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Eclipse Jetty 8 was released on September 1, 2011. Its most recent patch is 8.2.0.v20160908, published September 8, 2016.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in 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 →
All Eclipse Jetty Versions
| Version | Latest | EOL Date | Status |
|---|
| 7 |
7.6.21.v20160908 |
Supported |
EOL |
| → 8 |
8.2.0.v20160908 |
Supported |
EOL |
| 9.0 |
9.0.7.v20131107 |
Supported |
EOL |
| 9.1 |
9.1.6.v20160112 |
Supported |
EOL |
| 9.2 |
9.2.30.v20200428 |
Mar 8, 2018 |
EOL |
| 9.3 |
9.3.30.v20211001 |
Dec 7, 2020 |
EOL |
| 9.4 |
9.4.58.v20250814 |
Jan 2025 |
EOL |
| 10 |
10.0.26 |
Jan 1, 2025 |
EOL |
What does Eclipse Jetty 8 end of life mean?
When Eclipse Jetty 8 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 Eclipse Jetty 8 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Eclipse Jetty 12.1 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Eclipse Jetty 8 reach end of life?
Eclipse Jetty 8 has already reached end of life, though the vendor has not published an exact date.
Is Eclipse Jetty 8 still supported?
No. Eclipse Jetty 8 reached end of life on an unpublished date and is no longer receiving security patches.
What should I upgrade to from Eclipse Jetty 8?
The recommended upgrade from Eclipse Jetty 8 is
Eclipse Jetty 12.1 — the latest actively supported version. Check the
Eclipse Jetty full timeline for all supported versions.
What are the security risks of running Eclipse Jetty 8 past EOL?
Since Eclipse Jetty 8 reached end of life, the maintainers no longer issue 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 Eclipse Jetty should migrate immediately or implement compensating controls.