Complete end-of-life dates, support windows, and security status for all Eclipse Jetty versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 7 | 7.6.21.v20160908 | Oct 5, 2009 | Dec 31, 2014 | 4147 days past EOL | EOL |
| 8 | 8.2.0.v20160908 | Sep 1, 2011 | Dec 31, 2014 | 4147 days past EOL | EOL |
| 9.0 | 9.0.7.v20131107 | Mar 8, 2013 | Dec 31, 2013 | 4512 days past EOL | EOL |
| 9.1 | 9.1.6.v20160112 | Nov 15, 2013 | Dec 31, 2014 | 4147 days past EOL | EOL |
| 9.2 | 9.2.30.v20200428 | May 23, 2014 | Mar 8, 2018 | 2984 days past EOL | EOL |
| 9.3 | 9.3.30.v20211001 | Jun 1, 2015 | Dec 7, 2020 | 1979 days past EOL | EOL |
| 9.4 | 9.4.58.v20250814 | Dec 7, 2016 | Aug 14, 2025 | 268 days past EOL | EOL |
| 10 | 10.0.26 | Dec 2, 2020 | Jan 1, 2025 | 493 days past EOL | EOL |
| 11 | 11.0.26 | Dec 2, 2020 | Jan 1, 2025 | 493 days past EOL | EOL |
| 12.0 | 12.0.35 | Aug 7, 2023 | Already EOL | Supported | Active |
| 12.1 | 12.1.9 | Aug 18, 2025 | Already EOL | Supported | Active |
When a Eclipse Jetty version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Eclipse Jetty should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →