Tomcat 5 · Version Status
Tomcat 5 End of Life Date
Tomcat 5 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Tomcat 5 is past end of life. This version no longer receives security patches. 4969 days past EOL — migrate to a supported version immediately.
EOL Date
Sep 30, 2012
4969 days past EOL
Latest Release
5.5.36
Standard release
Release Date
Sep 6, 2003
Tomcat 5 series
| Version | Latest | EOL Date | Status |
|---|
| → 5 |
5.5.36 |
Sep 30, 2012 |
EOL |
| 6 |
6.0.53 |
Dec 31, 2016 |
EOL |
| 7 |
7.0.109 |
Mar 31, 2021 |
EOL |
| 8.0 |
8.0.53 |
Jun 30, 2018 |
EOL |
| 8.5 |
8.5.100 |
Mar 31, 2024 |
EOL |
| 9.0 |
9.0.118 |
Mar 31, 2027 |
Active |
| 10.0 |
10.0.27 |
Oct 31, 2022 |
EOL |
| 10.1 |
10.1.55 |
EOL |
Active |
What does Tomcat 5 end of life mean?
When Tomcat 5 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 Tomcat 5 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Tomcat 11.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Tomcat 5 reach end of life?
Tomcat 5 reached end of life on September 30, 2012. This version is no longer receiving security patches.
Is Tomcat 5 still supported?
No. Tomcat 5 reached end of life on September 30, 2012 and is no longer receiving security patches.
What should I upgrade to from Tomcat 5?
The recommended upgrade from Tomcat 5 is
Tomcat 11.0 — the latest actively supported version. Check the
Tomcat full timeline for all supported versions.
What are the security risks of running Tomcat 5 past EOL?
When Tomcat 5 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Tomcat should migrate immediately or implement compensating controls.