← Search results
CVE-LINKED INVENTORY126 SECURITY RECORDS
Apache Software Foundation
Apache Tomcat
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2019-17563 | 23 Dec 2019 | 9.0.0.M1 to 9.0.29; 8.5.0 to 8.5.49; 7.0.0 to 7.0.98 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2018-11784 | 4 Oct 2018 | 9.0.0.M1 to 9.0.11; 8.5.0 to 8.5.33; 7.0.23 to 7.0.90 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2018-8037 | 2 Aug 2018 | 9.0.0.M9 to 9.0.9; 8.5.5 to 8.5.31 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2018-1336 | 2 Aug 2018 | 9.0.0.M9 to 9.0.7; 8.5.0 to 8.5.30; 8.0.0.RC1 to 8.0.51; 7.0.28 to 7.0.86 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-8034 | 1 Aug 2018 | 9.0.0.M1 to 9.0.9; 8.5.0 to 8.5.31; 8.0.0.RC1 to 8.0.52; 7.0.35 to 7.0.88 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2018-8014 | 16 May 2018 | 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 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2018-1304 | 28 Feb 2018 | Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49, 7.0.0 to 7.0.84 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2018-1305 | 23 Feb 2018 | Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49, 7.0.0 to 7.0.84 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-15706 | 31 Jan 2018 | 9.0.0.M22 to 9.0.1; 8.5.16 to 8.5.23; 8.0.45 to 8.0.47; 7.0.79 to 7.0.82 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-12616 | 19 Sep 2017 | 7.0.0 to 7.0.80 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-7675 | 11 Aug 2017 | 9.0.0.M1 to 9.0.0.M21; 8.5.0 to 8.5.15 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-7674 | 11 Aug 2017 | 9.0.0.M1 to 9.0.0.M21; 8.5.0 to 8.5.15; 8.0.0.RC1 to 8.0.44; 7.0.41 to 7.0.78 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2016-6796 | 11 Aug 2017 | 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; 6.0.0 to 6.0.45 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2016-8745 | 10 Aug 2017 | 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; 6.0.16 to 6.0.48 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2016-6817 | 10 Aug 2017 | 9.0.0.M1 to 9.0.0.M11; 8.5.0 to 8.5.6 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2016-6797 | 10 Aug 2017 | 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; 6.0.0 to 6.0.45 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2016-6794 | 10 Aug 2017 | 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; 6.0.0 to 6.0.45 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2016-5018 | 10 Aug 2017 | 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; 6.0.0 to 6.0.45 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2016-0762 | 10 Aug 2017 | 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; 6.0.0 to 6.0.45 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-5664 | 6 Jun 2017 | 9.0.0.M1 to 9.0.0.M20; 8.5.0 to 8.5.14; 8.0.0.RC1 to 8.0.43; 7.0.0 to 7.0.77 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2017-5651 | 17 Apr 2017 | 9.0.0.M1 to 9.0.0.M18; 8.5.0 to 8.5.12 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-5650 | 17 Apr 2017 | 9.0.0.M1 to 9.0.0.M18; 8.5.0 to 8.5.12 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2017-5648 | 17 Apr 2017 | 9.0.0.M1 to 9.0.0.M17; 8.5.0 to 8.5.11; 8.0.0.RC1 to 8.0.41; 7.0.0 to 7.0.75 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-5647 | 17 Apr 2017 | 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; 6.0.0 to 6.0.52 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2016-6816 | 20 Mar 2017 | 9.0.0.M1 to 9.0.0.M11; 8.5.0 to 8.5.6; 8.0.0.RC1 to 8.0.38; 7.0.0 to 7.0.72; 6.0.0 to 6.0.47; Earlier, unsupported versions may also be affected. | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2016-8747 | 14 Mar 2017 | 8.5.7 to 8.5.9; 9.0.0.M11 to 9.0.0.M15 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.