Complete end-of-life dates, support windows, and security status for all Tomcat versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 5 | 5.5.36 | Sep 6, 2003 | Sep 30, 2012 | 4969 days past EOL | EOL |
| 6 | 6.0.53 | Oct 21, 2006 | Dec 31, 2016 | 3416 days past EOL | EOL |
| 7 | 7.0.109 | Jan 10, 2013 | Mar 31, 2021 | 1865 days past EOL | EOL |
| 8.0 | 8.0.53 | Jan 29, 2014 | Jun 30, 2018 | 2870 days past EOL | EOL |
| 8.5 | 8.5.100 | Mar 17, 2016 | Mar 31, 2024 | 769 days past EOL | EOL |
| 9.0 | 9.0.118 | Sep 27, 2017 | Mar 31, 2027 | 326 days remaining | Active |
| 10.0 | 10.0.27 | Dec 3, 2020 | Oct 31, 2022 | 1286 days past EOL | EOL |
| 10.1 | 10.1.55 | Sep 23, 2022 | Already EOL | Supported | Active |
| 11.0 | 11.0.22 | Oct 3, 2024 | Already EOL | Supported | Active |
When a Tomcat 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 Tomcat 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 →