LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Older Apache Tomcat versions accepted invalid characters in the HTTP request line. When paired with a proxy that interpreted those characters differently, an attacker could manipulate responses, enabling cache poisoning, cross-site scripting, or exposure of other users' request data. Most relevant exposure is internet-facing Tomcat behind reverse proxies, load balancers, or caching layers. Affected ranges include Tomcat 9.0.0.M1-M11, 8.5.0-8.5.6, 8.0.0.RC1-8.0.38, 7.0.0-7.0.72, and 6.0.0-6.0.47. Treat this as a prioritized remediation item for exposed Tomcat services behind proxies or caches. The issue can affect users and sensitive data, but urgency is highest where affected versions are reachable through intermediaries. Mitigation focus: Upgrade Tomcat to a fixed release for the deployed major version.; Use Tomcat 9.0.0.M13, 8.5.8, 8.0.39, 7.0.73, 6.0.48, or later.; Review vendor advisories for packaged Tomcat builds from Red Hat, Debian, Oracle, and NetApp..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-6816 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
25Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache Tomcat9.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.Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.