CVE-2016-5018: Critical severity Apache Tomcat vulnerability

Published Nov 1, 2016
·
Updated

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. ...

Other sources

The following flaw was found in Tomcat:

A malicious web application was able to bypass a configured SecurityManager via a Tomcat utility method that was accessible to web applications.

Upstream patches:

6.0.47: https://svn.apache.org/viewvc?view=revision&revision=1754904 7.0.72: https://svn.apache.org/viewvc?view=revision&revision=1754902 8.5.5: https://svn.apache.org/viewvc?view=revision&revision=1754900 8.0.37: https://svn.apache.org/viewvc?view=revision&revision=1754901

External References:

https://tomcat.apache.org/security-6.html#FixedinApacheTomcat6.0.47 https://tomcat.apache.org/security-7.html#FixedinApacheTomcat7.0.72 https://tomcat.apache.org/security-8.html#FixedinApacheTomcat8.5.5and8.0.37

— Red Hat

Affected Software

57 affected componentsFixes available
redhat/tomcat<6.0.47
6.0.47
redhat/tomcat<7.0.72
7.0.72
redhat/tomcat<8.5.5
8.5.5
redhat/tomcat<8.0.37
8.0.37
maven/org.apache.tomcat.embed:tomcat-embed-jasper>=6.0.0<=6.0.45
6.0.47
maven/org.apache.tomcat.embed:tomcat-embed-jasper>=7.0.0<=7.0.70
7.0.72
maven/org.apache.tomcat.embed:tomcat-embed-jasper>=8.0.0RC1<=8.0.36
8.0.37
maven/org.apache.tomcat.embed:tomcat-embed-jasper>=8.5.0<=8.5.4
8.5.5
maven/org.apache.tomcat.embed:tomcat-embed-jasper>=9.0.0.M1<=9.0.0.M9
9.0.0.M10
maven/org.apache.tomcat:jasper>=6.0.0<=6.0.45
6.0.47
maven/org.apache.tomcat:tomcat-jasper>=7.0.0<=7.0.70
7.0.72
maven/org.apache.tomcat:tomcat-jasper>=8.0.0RC1<=8.0.36
8.0.37
maven/org.apache.tomcat:tomcat-jasper>=8.5.0<=8.5.4
8.5.5
maven/org.apache.tomcat:tomcat-jasper>=9.0.0.M1<=9.0.0.M9
9.0.0.M10
debian/tomcat6
Apache Tomcat>=6.0.0<=6.0.45
Apache Tomcat>=7.0.0<=7.0.70
Apache Tomcat>=8.0<=8.0.36
Apache Tomcat>=8.5.0<=8.5.4
Apache Tomcat=9.0.0-milestone1
Apache Tomcat=9.0.0-milestone2
Apache Tomcat=9.0.0-milestone3
Apache Tomcat=9.0.0-milestone4
Apache Tomcat=9.0.0-milestone5
Apache Tomcat=9.0.0-milestone6
Apache Tomcat=9.0.0-milestone7
Apache Tomcat=9.0.0-milestone8
Apache Tomcat=9.0.0-milestone9
NetApp OnCommand Insight
NetApp Oncommand Shift
NetApp Snap Creator Framework
Canonical Ubuntu Linux=16.04
Debian Debian Linux=8.0
redhat JBoss Enterprise Application Platform=6.4
redhat Jboss Enterprise Web Server=3.0.0
redhat Enterprise Linux Desktop=7.0
redhat Enterprise Linux Eus=7.4
redhat Enterprise Linux Eus=7.5
redhat Enterprise Linux Eus=7.6
redhat Enterprise Linux Eus=7.7
redhat Enterprise Linux Server=7.0
redhat Enterprise Linux Server Aus=7.4
redhat Enterprise Linux Server Aus=7.6
redhat Enterprise Linux Server Aus=7.7
redhat Enterprise Linux Server Tus=7.6
redhat Enterprise Linux Server Tus=7.7
redhat Enterprise Linux Workstation=7.0
Oracle Tekelec Platform Distribution>=7.4.0<=7.7.1
Apache Tomcat=9.0.0-m1
Apache Tomcat=9.0.0-m2
Apache Tomcat=9.0.0-m3
Apache Tomcat=9.0.0-m4
Apache Tomcat=9.0.0-m5
Apache Tomcat=9.0.0-m6
Apache Tomcat=9.0.0-m7
Apache Tomcat=9.0.0-m8
Apache Tomcat=9.0.0-m9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-jasper to a version that resolves this vulnerability.

    Fixed in 6.0.47
  2. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-jasper to a version that resolves this vulnerability.

    Fixed in 7.0.72
  3. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-jasper to a version that resolves this vulnerability.

    Fixed in 8.0.37
  4. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-jasper to a version that resolves this vulnerability.

    Fixed in 8.5.5
  5. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-jasper to a version that resolves this vulnerability.

    Fixed in 9.0.0.M10
  6. Upgrade

    Upgrade maven/org.apache.tomcat:jasper to a version that resolves this vulnerability.

    Fixed in 6.0.47
  7. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-jasper to a version that resolves this vulnerability.

    Fixed in 7.0.72
  8. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-jasper to a version that resolves this vulnerability.

    Fixed in 8.0.37
  9. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-jasper to a version that resolves this vulnerability.

    Fixed in 8.5.5
  10. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-jasper to a version that resolves this vulnerability.

    Fixed in 9.0.0.M10
  11. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 6.0.47
  12. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 7.0.72
  13. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 8.5.5
  14. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 8.0.37
  15. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 6.0.47
  16. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 7.0.72
  17. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 8.5.5
  18. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 8.0.37

Event History

Nov 1, 2016
Data Sourced
via Red Hat·10:02 AM
DescriptionSeverityAffected Software
Aug 10, 2017
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
DescriptionWeakness
Data Sourced
via NVD·04:29 PM
RemedyDescriptionSeverityAffected Software
May 13, 2022
Advisory Published
via GitHub·01:02 AM
Aug 22, 2025
Data Sourced
via Ubuntu·02:26 AM
RemedyDescriptionSeverityAffected Software
Sep 23, 2025
Data Sourced
via Launchpad·02:34 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2016-5018?

CVE-2016-5018 is classified as a moderate severity vulnerability affecting various versions of Apache Tomcat.

2

How do I fix CVE-2016-5018?

To fix CVE-2016-5018, update Apache Tomcat to one of the fixed versions, such as 6.0.47, 7.0.72, 8.0.37, 8.5.5, or 9.0.0.M10.

3

What versions of Apache Tomcat are affected by CVE-2016-5018?

CVE-2016-5018 affects 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.

4

What type of vulnerability is CVE-2016-5018?

CVE-2016-5018 is a security vulnerability that allows a malicious web application to bypass a configured SecurityManager in Apache Tomcat.

5

Who should be concerned about CVE-2016-5018?

Organizations and individuals using vulnerable versions of Apache Tomcat should be concerned about CVE-2016-5018 due to its potential security implications.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203