Eclipse Jetty 7 End of Life Date
Eclipse Jetty 7 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
Eclipse Jetty 7 was released on October 5, 2009 and support ended on December 31, 2014 — a supported lifespan of 5 years and 3 months, longer than the 4 years and 1 month median for Eclipse Jetty releases. The last patch it will ever receive is 7.6.21.v20160908, published September 8, 2016 — 1 year and 8 months after the published end-of-life date. It has been without security patches for 11 years and 7 months. 6 newer Eclipse Jetty releases have shipped since.
Commercial vendors offer security patches beyond EOL. Right now that coverage spans Eclipse Jetty 9, 10, 11. Compare your options.
Compare Options →| Version | Latest | EOL Date | Status |
|---|---|---|---|
| → 7 | 7.6.21.v20160908 | Dec 31, 2014 | EOL |
| 8 | 8.2.0.v20160908 | Dec 31, 2014 | EOL |
| 9.0 | 9.0.7.v20131107 | Dec 31, 2013 | EOL |
| 9.1 | 9.1.6.v20160112 | Dec 31, 2014 | 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 | Aug 14, 2025 | EOL |
| 10 | 10.0.26 | Jan 1, 2025 | EOL |
What does Eclipse Jetty 7 end of life mean?
When Eclipse Jetty 7 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 Eclipse Jetty 7 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Eclipse Jetty 12.1 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.