ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2016-6796

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…

Published Aug 11, 2017 · catalog updated Oct 8, 2026 · the affected product

Last checked Nov 9, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2016-6796. EPSS is 8.32%. Act only if a listed version of the affected product is installed.

Gaps on this record

  • No plain product name is stored. The page cannot tell you which product to check.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
8.32%
Remediation
Version ranges on file
Affected products
cpe apache/tomcat

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe apache/tomcat9.0.0
  • cpe apache/tomcat>= 6.0.0, <= 6.0.45
  • cpe apache/tomcat>= 7.0.0, <= 7.0.70
  • cpe apache/tomcat>= 8.0, <= 8.0.36
  • cpe apache/tomcat>= 8.5.0, <= 8.5.4

How to fix CVE-2016-6796

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2016-6796. EPSS is 8.32%. Act only if a listed version of the affected product is installed.

Which versions are affected?

Compare what you have installed with 9.0.0, >= 6.0.0, <= 6.0.45, >= 7.0.0, <= 7.0.70, >= 8.0, <= 8.0.36, >= 8.5.0, <= 8.5.4. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 8.32%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Apache Tomcat security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Aug 11, 2017 · Monitored products — critical

    Detected

    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.

  2. Oct 8, 2026 · Monitored products — critical

    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.

Sources

  • CVE.orgVulnerability recordCVE-2016-6796

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2016-6796

    30-day exploitation probability 8.32%

    first.org
  • Monitored products — criticalVendor advisoryCVE-2016-6796

    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.

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 9, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSNov 9, 2026
  • CVE.orgNov 4, 2026
  • Monitored products — criticalNov 3, 2026