ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2016-6816

The code in Apache Tomcat 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, and 6.0.0 to 6.0.47 that parsed the HTTP request line permitted…

Published Mar 20, 2017 · catalog updated Jun 17, 2026 · the affected product

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

Check this week

CVE-2016-6816 is not in CISA KEV. FIRST estimates a 39.63% chance of exploitation in the next 30 days. Check whether you run the affected product.

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.1
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
39.63%
Remediation
Advisory link
Affected products
cpe apache/tomcat

The code in Apache Tomcat 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, and 6.0.0 to 6.0.47 that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack and/or obtain sensitive information from requests other then their own.

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/tomcat6.0.0
  • cpe apache/tomcat6.0.1
  • cpe apache/tomcat6.0.2
  • cpe apache/tomcat6.0.3
  • cpe apache/tomcat6.0.4
  • cpe apache/tomcat6.0.5

How to fix CVE-2016-6816

What to do

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

Should you patch?

CVE-2016-6816 is not in CISA KEV. FIRST estimates a 39.63% chance of exploitation in the next 30 days. Check whether you run the affected product.

Which versions are affected?

Compare what you have installed with 6.0.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-20: Improper Input Validation. EPSS 39.63%. 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. Mar 20, 2017 · Monitored products — critical

    Detected

    The code in Apache Tomcat 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, and 6.0.0 to 6.0.47 that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the att

  2. Jun 17, 2026 · Monitored products — critical

    Updated

    The code in Apache Tomcat 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, and 6.0.0 to 6.0.47 that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the att

Sources

  • CVE.orgVulnerability recordCVE-2016-6816

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2016-6816

    30-day exploitation probability 39.63%

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

    The code in Apache Tomcat 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, and 6.0.0 to 6.0.47 that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the att

    nvd.nist.gov

References

Freshness

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

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