CVE Intelligence
High Info disclosure

CVE-2017-12616 — Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat

When using a VirtualDirContext with Apache Tomcat 7.0.0 to 7.0.80 it was possible to bypass security constraints and/or view the source code of JSPs for resources served by the VirtualDirContext using a specially crafted request.

Published Sep 19, 2017 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: apache

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 70.1% (30-day exploitation probability)+15
  • Technical severity (high)+6
  • Automatable exploitation (SSVC)+3

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
70.12%
ahead of 99% of scored CVEs · Oct 15, 2026
Affects
Apache Software Foundation
Tomcat and 1 more
CVSS base
7.5
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
Yes
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-catalina: fixed in version 7.0.81 — 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, Maven Org.apache.tomcat:tomcat-catalina).
  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 99% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Apache Software Foundation Tomcat version 7.0.47version 7.0.59version 7.0.58version 7.0.57version 7.0.56version 7.0.55version 7.0.54version 7.0.51
and 74 more version 7.0.50version 7.0.49version 7.0.48version 7.0.60version 7.0.46version 7.0.45version 7.0.44version 7.0.43version 7.0.42version 7.0.41version 7.0.40version 7.0.39version 7.0.38version 7.0.70version 7.0.80version 7.0.79version 7.0.77version 7.0.76version 7.0.75version 7.0.74version 7.0.73version 7.0.72version 7.0.71version 7.0.0-betaversion 7.0.69version 7.0.68version 7.0.67version 7.0.66version 7.0.65version 7.0.64version 7.0.63version 7.0.62version 7.0.61version 7.0.6version 7.0.16version 7.0.15version 7.0.14version 7.0.13version 7.0.12version 7.0.11version 7.0.10version 7.0.9version 7.0.8version 7.0.7version 7.0.36version 7.0.5-betaversion 7.0.5version 7.0.4-betaversion 7.0.4version 7.0.3version 7.0.2-betaversion 7.0.2version 7.0.1version 7.0.0version 7.0.18version 7.0.37version 7.0.35version 7.0.34version 7.0.33version 7.0.32version 7.0.31version 7.0.30version 7.0.29version 7.0.28version 7.0.27version 7.0.26version 7.0.25version 7.0.24version 7.0.23version 7.0.22version 7.0.21version 7.0.20version 7.0.19version 7.0.17
Vulnerable NIST National Vulnerability Database
Apache Software Foundation Tomcat version 7.0.0 to 7.0.80 Vulnerable CVE Program (cve.org) e CISA ADP
Maven Org.apache.tomcat:tomcat-catalina ≥ 7.0.0 and ≤ 7.0.80 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Every base score collected

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

ScoreVersionSeverityExpl.ImpactScored by
7.5 CVSS 3.0 High 3.9 3.6 nvd@nist.gov via NIST National Vulnerability Database
7.5 CVSS 3.0 High — — GitHub, Inc. via GitHub Security Advisories
5.0 CVSS 2.0 Medium 10.0 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-200 · Exposure of Sensitive Information

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).
  • Look for anomalous data read/export volumes and access to sensitive records.
web/proxy/WAF logsnetwork IDS/IPSapplication logsauthentication 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-catalina
    Oct 15, 2026 · GitHub Security Advisories
  • Affected products added · apache software foundation/apache tomcat
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 15, 2026
  • Affected products added · apache/tomcat
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.5
    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
  • 2017
  • CVE published
    Sep 19, 2017 · apache

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

21 on the record

Elsewhere on this site

Apache Software Foundation
every CVE for this vendor
Info disclosure
same class
CWE-200
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-55956 Apache Tomcat: Security constraints for default servlet ignored method 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-55957 Apache Tomcat: Authentication bypass with JNDIRealm and GSSAPI authenticated bind Jun 29, 2026
  • CVE-2026-50229 Apache Tomcat: XSS in number guess example Jun 29, 2026
  • CVE-2026-53404 Apache Tomcat: Bad ornext processing in RewriteValve 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-2017-12616 is "Exposure of Sensitive Information to an Unauthorized Actor 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 7.5 describes technical severity. EPSS 70.12% 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.