● Branch of Apache Tomcat
Apache Tomcat 7
Apache Tomcat 7 reached end of life on 31 March 2021. Move to 9.0.124 or newer.
Data: .
Records with no fixed release for 7
These records name the branch as affected and name no release that ends the range.
| Record | Signs of exploitation | Fixed in |
|---|---|---|
| CVE-2017-12617Remote Code Execution8.1 High · published 3 October 2017 | On CISA's list Metasploit module Exploit-DB entry EPSS 0.50 or more | The record names no fixed release for 9.0, 8.5, 8.0 and 7. |
| CVE-2017-12615on Windows Remote Code Execution8.1 High · published 19 September 2017 | On CISA's list Exploit-DB entry EPSS 0.50 or more | The record names no fixed release for 7. |
| CVE-2019-0232When running on Windows with enableCmdLineArguments enabled, the CGI Servlet in Apache Tomcat 9.0.0.M1 to 9.0.17, 8.5.0 to 8.5.39 and 7.0.0 to 7.0.93 is vulnerable to Remote Code Execution due to a…published 15 April 2019 | Metasploit module Exploit-DB entry EPSS 0.50 or more | The record names no fixed release for 9.0, 8.5 and 7. |
| CVE-2018-11784When the default servlet in Apache Tomcat versions 9.0.0.M1 to 9.0.11, 8.5.0 to 8.5.33 and 7.0.23 to 7.0.90 returned a redirect to a directory (e.g. redirecting to '/foo/' when the user requested…published 4 October 2018 | Exploit-DB entry EPSS 0.50 or more | The record names no fixed release for 9.0, 8.5 and 7. |
| CVE-2017-12616When using a VirtualDirContext with Apache Tomcat 7.0.0 to 7.0.80 it was possible to bypass security constraints and/or view the source code of JSPs for resources served by the VirtualDirContext…published 19 September 2017 | EPSS 0.50 or more | The record names no fixed release for 7. |
| CVE-2018-8034The host name verification when using TLS with the WebSocket client was missing. It is now enabled by default. Versions Affected: Apache Tomcat 9.0.0.M1 to 9.0.9, 8.5.0 to 8.5.31, 8.0.0.RC1 to…7.5 High · published 1 August 2018 | None | The record names no fixed release for 9.0, 8.5, 8.0 and 7. |
| CVE-2018-8014The defaults settings for the CORS filter provided in Apache Tomcat 9.0.0.M1 to 9.0.8, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, 7.0.41 to 7.0.88 are insecure and enable 'supportsCredentials' for all…published 16 May 2018 | None | The record names no fixed release for 9.0, 8.5, 8.0 and 7. |
| CVE-2018-1336An improper handing of overflow in the UTF-8 decoder with supplementary characters can lead to an infinite loop in the decoder causing a Denial of Service. Versions Affected: Apache Tomcat 9.0.0.M9…published 2 August 2018 | None | The record names no fixed release for 9.0, 8.5, 8.0 and 7. |
| CVE-2017-5664The error page mechanism of the Java Servlet Specification requires that, when an error occurs and an error page is configured for the error that occurred, the original request and response are…published 6 June 2017 | None | The record names no fixed release for 9.0, 8.5, 8.0 and 7. |
| CVE-2017-5647A bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results…published 17 April 2017 | None | The record names no fixed release for 9.0, 8.5, 8.0, 7 and 6. |
| CVE-2016-8745A bug in the error handling of the send file code for the NIO HTTP connector in Apache Tomcat 9.0.0.M1 to 9.0.0.M13, 8.5.0 to 8.5.8, 8.0.0.RC1 to 8.0.39, 7.0.0 to 7.0.73 and 6.0.16 to 6.0.48…published 10 August 2017 | None | The record names no fixed release for 9.0, 8.5, 8.0, 7 and 6. |
| CVE-2017-5648While investigating bug 60718, it was noticed that some calls to application listeners in Apache Tomcat 9.0.0.M1 to 9.0.0.M17, 8.5.0 to 8.5.11, 8.0.0.RC1 to 8.0.41, and 7.0.0 to 7.0.75 did not use…published 17 April 2017 | None | The record names no fixed release for 9.0, 8.5, 8.0 and 7. |
| CVE-2019-17563When using FORM authentication with Apache Tomcat 9.0.0.M1 to 9.0.29, 8.5.0 to 8.5.49 and 7.0.0 to 7.0.98 there was a narrow window where an attacker could perform a session fixation attack. The…published 23 December 2019 | None | The record names no fixed release for 9.0, 8.5 and 7. |
| CVE-2016-5018In Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 a malicious web application was able to bypass a configured SecurityManager via a…published 10 August 2017 | None | The record names no fixed release for 9.0, 8.5, 8.0, 7 and 6. |
| CVE-2017-7674The CORS Filter in Apache Tomcat 9.0.0.M1 to 9.0.0.M21, 8.5.0 to 8.5.15, 8.0.0.RC1 to 8.0.44 and 7.0.41 to 7.0.78 did not add an HTTP Vary header indicating that the response varies depending on…published 11 August 2017 | None | The record names no fixed release for 9.0, 8.5, 8.0 and 7. |
| CVE-2016-6797The ResourceLinkFactory implementation in Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 did not limit web application access to global…published 10 August 2017 | None | The record names no fixed release for 9.0, 8.5, 8.0, 7 and 6. |
| CVE-2016-6796A malicious web application running on Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 was able to bypass a configured SecurityManager…published 11 August 2017 | None | The record names no fixed release for 9.0, 8.5, 8.0, 7 and 6. |
| CVE-2016-0762The Realm implementations in Apache Tomcat versions 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 did not process the supplied password if the…published 10 August 2017 | None | The record names no fixed release for 9.0, 8.5, 8.0, 7 and 6. |
| CVE-2016-6794When a SecurityManager is configured, a web application's ability to read system properties should be controlled by the SecurityManager. In Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4…published 10 August 2017 | None | The record names no fixed release for 9.0, 8.5, 8.0, 7 and 6. |
| CVE-2017-15706As part of the fix for bug 61201, the documentation for Apache Tomcat 9.0.0.M22 to 9.0.1, 8.5.16 to 8.5.23, 8.0.45 to 8.0.47 and 7.0.79 to 7.0.82 included an updated description of the search…published 31 January 2018 | None | The record names no fixed release for 9.0, 8.5, 8.0 and 7. |
| CVE-2026-50229Apache Tomcat: XSS in number guess example6.1 Medium · published 29 June 2026 | None | The record names no fixed release for 9.0, 8.5, 7, 11.0 and 10.1. |
| CVE-2026-55957Apache Tomcat: Authentication bypass with JNDIRealm and GSSAPI authenticated bind7.3 High · published 29 June 2026 | None | The record names no fixed release for 9.0, 8.5, 7, 11.0 and 10.1. |
| CVE-2024-38286Apache Tomcat: Denial of Service8.6 High · published 7 November 2024 | None | The record names no fixed release for 9.0, 8.5, 7, 11.0 and 10.1. |
| CVE-2026-101296Apache Tomcat: JNDIRealm bind credential validation fails open for non-GSSAPI SASL mechanisms9.1 Critical · published 20 October 2026 | None | The record names no fixed release for 9.0, 8.5, 7, 11.0 and 10.1. |
| CVE-2026-87022Apache Tomcat: WebSocket message smuggling with per-message-deflate7.5 High · published 23 September 2026 | None | The record names no fixed release for 9.0, 8.5, 7, 11.0 and 10.1. |
| CVE-2026-78383Apache Tomcat: AJP DoS via missing request body7.5 High · published 23 September 2026 | None | The record names no fixed release for 9.0, 8.5, 7, 11.0 and 10.1. |
| CVE-2026-76183Apache Tomcat: Bypass of security constraints for WebSocket endpoints9.8 Critical · published 23 September 2026 | None | The record names no fixed release for 9.0, 8.5, 7, 11.0 and 10.1. |
| CVE-2026-68525Apache Tomcat: Redirect after FORM auth may bypass method specific constraints9.1 Critical · published 25 August 2026 | None | The record names no fixed release for 9.0, 8.5, 7, 11.0 and 10.1. |
| CVE-2026-65905Apache Tomcat: Limited replay attack possible with DIGEST authentication9.8 Critical · published 25 August 2026 | None | The record names no fixed release for 9.0, 8.5, 7, 11.0 and 10.1. |
| CVE-2026-65182Apache Tomcat: Bypass longest prefix security constraint9.1 Critical · published 25 August 2026 | None | The record names no fixed release for 9.0, 8.5, 7, 11.0 and 10.1. |
| CVE-2026-59084Apache Tomcat: EncryptInterceptor requirements not clearly documented9.1 Critical · published 14 July 2026 | None | The record names no fixed release for 9.0, 8.5, 7, 11.0 and 10.1. |
| CVE-2026-55956Apache Tomcat: Security constraints for default servlet ignored method6.5 Medium · published 29 June 2026 | None | The record names no fixed release for 9.0, 8.5, 7, 11.0 and 10.1. |
| CVE-2026-43515Apache Tomcat: Security constraints not correctly applied9.1 Critical · published 12 May 2026 | None | The record names no fixed release for 9.0, 8.5, 7, 11.0 and 10.1. |
| CVE-2026-43513Apache Tomcat: LockOutRealm treats user names as case-sensitive7.5 High · published 12 May 2026 | None | The record names no fixed release for 9.0, 8.5, 7, 11.0 and 10.1. |
| CVE-2026-43512Apache Tomcat: Digest authenticator will authenticate any unknown user9.8 Critical · published 12 May 2026 | None | The record names no fixed release for 9.0, 8.5, 7, 11.0 and 10.1. |
| CVE-2026-42498Apache Tomcat: WebSocket authentication header exposure7.3 High · published 12 May 2026 | None | The record names no fixed release for 9.0, 8.5, 7, 11.0 and 10.1. |
| CVE-2026-24880Apache Tomcat: Request smuggling via invalid chunk extension7.5 High · published 9 April 2026 | None | The record names no fixed release for 9.0, 8.5, 7, 11.0 and 10.1. |
| CVE-2019-12418When Apache Tomcat 9.0.0.M1 to 9.0.28, 8.5.0 to 8.5.47, 7.0.0 and 7.0.97 is configured with the JMX Remote Lifecycle Listener, a local attacker without access to the Tomcat process or configuration…published 23 December 2019 | None | The record names no fixed release for 9.0, 8.5 and 7. |
| CVE-2026-121649Apache Tomcat: ExpiresFilter removes existing Cache-Control: private headerpublished 19 November 2026 | None | The record names no fixed release for 9.0, 8.5, 7, 11.0 and 10.1. |
| CVE-2026-118436Apache Tomcat: CGIServlet drops chunked POST body and can hang worker thread7.5 High · published 19 November 2026 | None | The record names no fixed release for 9.0, 8.5, 7, 11.0 and 10.1. |
and 11 more CVE records that this page reads
Apache Tomcat 7 in dates
| What | When |
|---|---|
| Released | 13 June 2010 |
| End of life | 31 March 2021 |
| Newest release | 7.0.109 (22 April 2021) |
What this page says
The lifecycle data lists 7.0.109 (22 April 2021) for Apache Tomcat 7, after its end of life on 31 March 2021. This page cannot tell whether that release fixes anything.
This page reads 118 CVE records that the Apache Software Foundation's CVE Numbering Authority has published since 31 March 2021 and that name Apache Tomcat. 14 of them are not placed on a branch. Of the others, 30 name Apache Tomcat 7.
No release of Apache Tomcat 7 is called safe here, because the branch has ended, whatever the records say of it.
A release is the fix of a record when the record's affected range for this branch ends before it. Dates are from the product lifecycle data credited under Sources.
Sources
- CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
- Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
- EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)