CVE-2016-6796: High severity Apache Tomcat vulnerability

Published Nov 1, 2016
·
Updated

A 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 via manipulation of the configuration parameters for the JSP Servlet.

Other sources

The following flaw was found in Tomcat:

A malicious web application was able to bypass a configured SecurityManager via manipulation of the configuration parameters for the JSP Servlet.

Upstream patches:

6.0.47: https://svn.apache.org/viewvc?view=rev&rev=1758496 https://svn.apache.org/viewvc?view=rev&rev=1763237

7.0.72: https://svn.apache.org/viewvc?view=rev&rev=1758495 https://svn.apache.org/viewvc?view=rev&rev=1763236

8.5.5: https://svn.apache.org/viewvc?view=rev&rev=1758493

8.0.37: https://svn.apache.org/viewvc?view=rev&rev=1758494 https://svn.apache.org/viewvc?view=rev&rev=1763234

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

54 affected componentsFixes available
debian/tomcat6
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:tomcat>=6.0.0<=6.0.45
6.0.46
maven/org.apache.tomcat:tomcat>=7.0.0<=7.0.70
7.0.71
maven/org.apache.tomcat:tomcat>=8.0.0.RC1<=8.0.36
8.0.37
maven/org.apache.tomcat:tomcat>=8.5.0<=8.5.4
8.5.5
maven/org.apache.tomcat:tomcat>=9.0.0.M1<=9.0.0.M9
9.0.0.M10
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
Debian Debian Linux=8.0
NetApp OnCommand Insight
NetApp Oncommand Shift
NetApp Snap Creator Framework
Canonical Ubuntu Linux=16.04
Oracle Tekelec Platform Distribution=7.4.0
Oracle Tekelec Platform Distribution=7.7.1
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
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
IBM InfoSphere Data Architect<=9.2.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 6.0.47
  2. Upgrade

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

    Fixed in 7.0.72
  3. Upgrade

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

    Fixed in 8.5.5
  4. Upgrade

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

    Fixed in 8.0.37
  5. Upgrade

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

    Fixed in 6.0.46
  6. Upgrade

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

    Fixed in 7.0.71
  7. Upgrade

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

    Fixed in 8.0.37
  8. Upgrade

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

    Fixed in 8.5.5
  9. Upgrade

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

    Fixed in 9.0.0.M10

Event History

Aug 11, 2017
CVE Published
via MITRE·02:00 AM
Data Sourced
via MITRE·02:00 AM
DescriptionWeakness
Data Sourced
via NVD·02:29 AM
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
Mar 4, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

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-6796?

CVE-2016-6796 has been classified as a high severity vulnerability due to its ability to bypass security restrictions.

2

How do I fix CVE-2016-6796?

To fix CVE-2016-6796, upgrade to Apache Tomcat version 6.0.47, 7.0.72, 8.0.37, 8.5.5, or 9.0.0.M10.

3

Which versions of Apache Tomcat are affected by CVE-2016-6796?

CVE-2016-6796 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

Is CVE-2016-6796 related to the JSP Servlet configuration?

Yes, CVE-2016-6796 specifically allows a malicious web application to bypass the configured SecurityManager through manipulation of JSP Servlet configuration parameters.

5

What impact does CVE-2016-6796 have on my application?

The impact of CVE-2016-6796 could lead to unauthorized access or modification of application data if exploited successfully.

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