CVE Intelligence
High

CVE-2015-5346 — Improper Neutralization of Input During Web Page Generation in Apache Tomcat

Session fixation vulnerability in Apache Tomcat 7.x before 7.0.66, 8.x before 8.0.30, and 9.x before 9.0.0.M2, when different session settings are used for deployments of multiple versions of the same web application, might allow remote attackers to hijack web sessions by leveraging use of a requestedSessionSSL field for an unintended request, related to CoyoteAdapter.java and Request.java.

Published Feb 24, 2016 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: redhat

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 10.6% (30-day exploitation probability)+14
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
10.57%
ahead of 96% of scored CVEs · Oct 14, 2026
Affects
Apache Software Foundation
Tomcat and 3 more
CVSS base
8.1
High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Maven Org.apache.tomcat:tomcat: fixed in version 9.0.0.M2 — github.com (GitHub Security Advisories)
  • Maven Org.apache.tomcat:tomcat: fixed in version 8.0.31 — github.com (GitHub Security Advisories)
  • Maven Org.apache.tomcat:tomcat: fixed in version 7.0.66 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Apache Software Foundation Tomcat, Canonical Ubuntu Linux, Debian Debian Linux…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. EPSS ahead of 96% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Apache Software Foundation Tomcat version 7.0.59version 8.0.0-rc3version 8.0.0-rc10version 8.0.0-rc1version 7.0.65version 7.0.64version 7.0.63version 7.0.62
and 58 more version 7.0.61version 8.0.0-rc5version 7.0.57version 7.0.56version 7.0.55version 7.0.54version 7.0.53version 7.0.52version 7.0.50version 7.0.47version 8.0.20version 8.0.29version 8.0.28version 8.0.27version 8.0.26version 8.0.24version 8.0.23version 8.0.22version 8.0.21version 7.0.42version 8.0.18version 8.0.17version 8.0.15version 8.0.14version 8.0.12version 8.0.11version 8.0.3version 8.0.1version 7.0.21version 9.0.0-milestone1version 7.0.0-betaversion 7.0.2-betaversion 7.0.4-betaversion 7.0.5-betaversion 7.0.6version 7.0.10version 7.0.11version 7.0.12version 7.0.14version 7.0.16version 7.0.19version 7.0.20version 7.0.22version 7.0.34version 7.0.41version 7.0.40version 7.0.39version 7.0.37version 7.0.35version 7.0.23version 7.0.33version 7.0.32version 7.0.30version 7.0.29version 7.0.28version 7.0.27version 7.0.26version 7.0.25
Vulnerable NIST National Vulnerability Database
Canonical Ubuntu Linux version 16.04version 15.10version 14.04version 12.04 Vulnerable NIST National Vulnerability Database
Debian Debian Linux version 8.0version 7.0 Vulnerable NIST National Vulnerability Database
Maven Org.apache.tomcat:tomcat version 9.0.0.M1≥ 8.0.0.RC1 and ≤ 8.0.30≥ 7.0.0 and ≤ 7.0.65 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.1 CVSS 3.0 High 2.2 5.9 nvd@nist.gov via NIST National Vulnerability Database
8.1 CVSS 3.0 High — — GitHub, Inc. via GitHub Security Advisories
6.8 CVSS 2.0 Medium 8.6 6.4 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 14, 2026 · GitHub Security Advisories
  • Affected products added · maven/org.apache.tomcat:tomcat
    Oct 14, 2026 · GitHub Security Advisories
  • SSVC assessment updated
    Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 14, 2026
  • Affected products added · apache/tomcat, canonical/ubuntu linux, debian/debian linux
    Oct 14, 2026 · NIST National Vulnerability Database
  • CVSS changed · 8.1
    Oct 14, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 14, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 14, 2026 · Alertas do Telegram
  • 2016
  • CVE published
    Feb 24, 2016 · redhat

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 14, 2026 – Oct 14, 2026

References

46 on the record

Elsewhere on this site

Apache Software Foundation
every CVE for this vendor

Related CVEs (same products)

  • CVE-2026-73180 Apache Tomcat: Authenticated WebSocket session survives end of HTTP session Aug 25, 2026
  • CVE-2026-65183 Apache Tomcat: TOCTOU when setting specific permissions for Unix Domain Sockets Aug 25, 2026
  • CVE-2026-66422 Apache Tomcat: Servlet role references can bypass declarative role constraints Aug 25, 2026
  • CVE-2026-65905 Apache Tomcat: Limited replay attack possible with DIGEST authentication Aug 25, 2026
  • CVE-2026-68525 Apache Tomcat: Redirect after FORM auth may bypass method specific constraints Aug 25, 2026
  • CVE-2026-65927 Apache Tomcat: RewriteValve [N] restarts at the second rule and may bypass access control Aug 25, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CWE classification.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2015-5346 is "Improper Neutralization of Input During Web Page Generation in Apache Tomcat", rated High. It affects Tomcat (Apache Software Foundation); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.1 describes technical severity. EPSS 10.57% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.