CVE Intelligence
High Access control

CVE-2016-0714 — Improper Access Control in Apache Tomcat

The session-persistence implementation in Apache Tomcat 6.x before 6.0.45, 7.x before 7.0.68, 8.x before 8.0.31, and 9.x before 9.0.0.M2 mishandles session attributes, which allows remote authenticated users to bypass intended SecurityManager restrictions and execute arbitrary code in a privileged context via a web application that places a crafted object in a session.

Published Feb 24, 2016 · Updated Oct 15, 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 13.1% (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
13.08%
ahead of 96% of scored CVEs · Oct 15, 2026
Affects
Apache Software Foundation
Tomcat and 3 more
CVSS base
8.8
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
Total
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.32 — github.com (GitHub Security Advisories)
  • Maven Org.apache.tomcat:tomcat: fixed in version 7.0.70 — github.com (GitHub Security Advisories)
  • Maven Org.apache.tomcat:tomcat: fixed in version 6.0.46 — 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. Apply the fixed version or the patch documented under Remediation.
  3. EPSS ahead of 96% of scored CVEs: prioritize it in the patch queue.
  4. Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Apache Software Foundation Tomcat version 6.0.0version 6.0.0-alphaversion 6.0.1version 6.0.1-alphaversion 6.0.2version 6.0.2-alphaversion 6.0.2-betaversion 6.0.4
and 90 more version 6.0.4-alphaversion 6.0.10version 6.0.11version 6.0.13version 6.0.14version 6.0.16version 6.0.18version 6.0.20version 6.0.24version 6.0.26version 6.0.28version 6.0.29version 6.0.30version 6.0.32version 6.0.33version 6.0.35version 6.0.36version 6.0.37version 6.0.39version 6.0.41version 6.0.43version 6.0.44version 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.21version 7.0.22version 7.0.23version 7.0.25version 7.0.26version 7.0.27version 7.0.28version 7.0.29version 7.0.30version 7.0.32version 7.0.33version 7.0.34version 7.0.35version 7.0.37version 7.0.39version 7.0.40version 7.0.41version 7.0.42version 7.0.47version 7.0.50version 7.0.52version 7.0.53version 7.0.54version 7.0.55version 7.0.56version 7.0.57version 7.0.59version 7.0.61version 7.0.62version 7.0.63version 7.0.64version 7.0.65version 7.0.67version 8.0.0-rc1version 8.0.0-rc10version 8.0.0-rc3version 8.0.0-rc5version 8.0.1version 8.0.3version 8.0.11version 8.0.12version 8.0.14version 8.0.15version 8.0.17version 8.0.18version 8.0.20version 8.0.21version 8.0.22version 8.0.23version 8.0.24version 8.0.26version 8.0.27version 8.0.28version 8.0.29version 8.0.30version 9.0.0-milestone1
Vulnerable NIST National Vulnerability Database
Canonical Ubuntu Linux version 12.04version 14.04version 15.10version 16.04 Vulnerable NIST National Vulnerability Database
Debian Debian Linux version 7.0version 8.0 Vulnerable NIST National Vulnerability Database
Maven Org.apache.tomcat:tomcat version 9.0.0.M1≥ 8.0.0.RC1 and < 8.0.32≥ 7.0.0 and < 7.0.70≥ 6.0.0 and < 6.0.46 Vulnerable GitHub Security Advisories

Attack characteristics

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

Attack vector
Network
Attack complexity
Low
Privileges required
Low
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.8 CVSS 3.0 High 2.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
8.8 CVSS 3.0 High — — GitHub, Inc. via GitHub Security Advisories
6.5 CVSS 2.0 Medium 8.0 6.4 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-264 · Permissions, Privileges, and Access Controls

Other CVEs with this weakness →

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).
  • Audit administrative actions and access to resources outside each user’s normal pattern.
web/proxy/WAF logsnetwork IDS/IPSauthentication logsapplication logs

Timeline

What happened to this CVE, newest first.

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

Source activity

Repeated readings are counted rather than listed.

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

References

71 on the record

Elsewhere on this site

Apache Software Foundation
every CVE for this vendor
Access control
same class
CWE-264
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-12996 A use-after-free in OpenVPN 2.6.0 through 2.6.20 and 2.7_alpha1 through 2.7.4 allows remote... Jul 30, 2026
  • CVE-2026-55956 Apache Tomcat: Security constraints for default servlet ignored method Jun 29, 2026
  • CVE-2026-55957 Apache Tomcat: Authentication bypass with JNDIRealm and GSSAPI authenticated bind Jun 29, 2026
  • CVE-2026-55276 Apache Tomcat: Logged effective web.xml is incomplete Jun 29, 2026
  • CVE-2026-55955 Apache Tomcat: EncryptInterceptor not protected against replay attacks Jun 29, 2026
  • CVE-2026-53434 Apache Tomcat CRL Configuration Flaw in FFM Connector (CWE-390) Jun 29, 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 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-2016-0714 is "Improper Access Control 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.8 describes technical severity. EPSS 13.08% 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.