Apache Tomcat 7 · Version Status
Apache Tomcat 7 End of Life Date
Apache Tomcat 7 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.
⚠
Apache Tomcat 7 is past end of life. This version no longer receives security patches. 2047 days past EOL — migrate to a supported version immediately.
EOL Date
Mar 31, 2021
2047 days past EOL
Latest Release
7.0.109
Standard release
Release Date
Jun 13, 2010
Apache Tomcat 7 series
Where these dates come from
End of lifeMar 31, 2021Vendor's own page, checked by a person · tomcat.apache.org · checked Sep 17, 2026high · 2 sources agree ReleaseJun 13, 2010Vendor's own page, checked by a person · tomcat.apache.org · checked Sep 17, 2026high · 2 sources agree 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
Apache Tomcat 7 was released on June 13, 2010 and support ended on March 31, 2021 — a supported lifespan of 10 years and 10 months, longer than the 9 years and 1 month median for Apache Tomcat releases. Its latest release on record is 7.0.109, published April 22, 2021 — 22 days after the published end-of-life date. It has been past its end-of-life date for 5 years and 7 months. 2 newer Apache Tomcat releases have shipped since.
Attack Surface
20/30 High tier
CISA KEV Exposure
20/20 Named in CISA 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 Apache Tomcat Versions
| 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.123 |
EOL |
Active |
| 10.0 |
10.0.27 |
Oct 31, 2022 |
EOL |
| 10.1 |
10.1.61 |
EOL |
Active |
What does Apache Tomcat 7 end of life mean?
When Apache Tomcat 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: 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 Apache Tomcat 7 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Apache Tomcat 11.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Apache Tomcat 7 reach end of life?
Apache Tomcat 7 reached end of life on March 31, 2021. This version is no longer receiving security patches.
Is Apache Tomcat 7 still supported?
No. Apache Tomcat 7 reached end of life on March 31, 2021 and is no longer receiving security patches.
What should I upgrade to from Apache Tomcat 7?
The recommended upgrade from Apache Tomcat 7 is
Apache Tomcat 11.0 — the latest actively supported version. Check the
Apache Tomcat full timeline for all supported versions.
What are the security risks of running Apache Tomcat 7 past EOL?
Since Apache Tomcat 7 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 Apache Tomcat should migrate immediately or implement compensating controls.