Eclipse Jetty 11 · Version Status
Eclipse Jetty 11 End of Life Date
Eclipse Jetty 11 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 11 is past end of life. This version no longer receives security patches. 675 days past EOL — migrate to a supported version immediately.
EOL Date
Jan 1, 2025
675 days past EOL
Latest Release
11.0.26
Standard release
Release Date
Dec 2, 2020
Eclipse Jetty 11 series
Where these dates come from
End of lifeJan 1, 2025endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees End of active supportJan 1, 2024endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseDec 2, 2020endoflife.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 11 was released on December 2, 2020 and support ended on January 1, 2025 — a supported lifespan of 4 years and 1 month, in line with the 4 years and 1 month median for Eclipse Jetty releases. Its most recent release is 11.0.26, published August 18, 2025. Standard support ended 1 year and 10 months ago. Security fixes now come only through extended support; without it this version is unpatched. 1 newer Eclipse Jetty release has shipped since.
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 11 end of life mean?
When Eclipse Jetty 11 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 11 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 11 reach end of life?
Eclipse Jetty 11 reached end of life on January 1, 2025. This version is no longer receiving security patches.
Is Eclipse Jetty 11 still supported?
No. Eclipse Jetty 11 reached end of life on January 1, 2025 and is no longer receiving security patches.
What should I upgrade to from Eclipse Jetty 11?
The recommended upgrade from Eclipse Jetty 11 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 11 past EOL?
Since Eclipse Jetty 11 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.