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.
CVE-2017-12616
“▲” beside the score: it is higher than NVD's CVSS score.
Score elevated to 8.6 because EPSS predicted 70% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.
- 61 internet-facing services (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
- High exploitation likelihood — EPSS 70%
A fix is available — apply it.
61 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2017-12616, in our KEV-Exposure radar’s Shodan-derived sample.
How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.
- CVSS v3
- 7.5
- EG Score
- 8.6HIGHhigh confidence
- EG Risk
- 77EG Risk 77/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation70% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 70%
- EPSS %ILE
- 99th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.6): severity, escalated by confirmed exploitation. This CVE's 8.6 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.5 HIGH): a likelihood of exploitation, not impact.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 70% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-21). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
September 19, 2017
Last Modified
October 15, 2026
Advisory Details (7)
Auto-updated Oct 15, 2026[SECURITY] [DLA 1400-1] tomcat7 security update
https://lists.debian.org/debian-lts-announce/2018/06/msg00008.htmlPony Mail
https://lists.apache.org/thread.html/1df9b4552464caa42047062fe7175da0da06c18ecc8daf99258bbda6%40%3Cannounce.tomcat.apache.org%3ESynology_SA_17_54_Tomcat | Synology Inc.
https://www.synology.com/support/security/Synology_SA_17_54_TomcatPatch Availability(4)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | tomcat7-user (7.0.68-1ubuntu0.4+esm3) @ xenial | 2026-10-15 | ubuntu |
| ubuntu | tomcat8-user (8.0.32-1ubuntu1.6) @ xenial | 2026-10-15 | ubuntu |
| redhat | patch | 2018-03-07 | redhat |
| redhat | tomcat-vault-0:1.1.6-1.Final_redhat_1.1.ep7.el7 | 2018-03-07 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(3 across 3 ecosystems)
Debian:7(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| tomcat7 | 7.0.28-4 ... 7.0.28-4+deb7u9 (15 versions) |
| — |
Debian:8(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| tomcat7 | 7.0.56-3 ... 7.0.56-3+deb8u9 (12 versions) |
| — |
Maven(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| org.apache.tomcat:tomcat-catalina | 7.0.0 ... 7.0.8 (55 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(4)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 8× in last 7d / 28× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 91 of 105 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 9 repeat rows among the latest 100 are merged into the row they repeat. The 14 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-23 16:26 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-10-22 16:27 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-10-22 10:57 UTCEG score recompute
- 2026-10-22 10:57 UTCVendor advisory
- 2026-10-21 16:27 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-10-20 16:27 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-10-19 16:26 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-10-18 10:40 UTCEG score recompute
- 2026-10-16 16:29 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-10-15 16:32 UTCEG score recompute
- 2026-10-15 16:32 UTCVendor advisory
- 2026-10-15 15:58 UTCEG score recompute
- 2026-10-15 15:58 UTCVendor advisory
- 2026-10-14 16:27 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-10-13 16:27 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-10-13 03:11 UTCVendor advisory
- 2026-10-12 20:35 UTCEG score recompute
- 2026-10-12 00:58 UTCEG score recompute
- 2026-10-10 19:55 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-10-09 20:02 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-10-07 23:54 UTCOSV refresh
- 2026-10-07 23:41 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-10-06 15:11 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-10-03 14:21 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-09-30 14:58 UTCEPSS rescoreEPSS 70% · 99th percentile
Show 66 moreShow fewer
- 2026-09-30 09:24 UTCEG score recompute
- 2026-09-26 15:53 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-09-24 13:59 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-09-18 19:22 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-09-18 06:06 UTCOSV refresh
- 2026-09-17 19:22 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-09-15 03:05 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-09-12 14:55 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-09-11 09:31 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-09-10 09:26 UTCEPSS rescoreEPSS 70% · 99th percentile
- 2026-09-07 15:56 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-09-04 13:56 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-09-04 05:01 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-09-02 14:07 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-30 19:13 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-30 06:30 UTCOSV refresh
- 2026-08-28 21:36 UTCEPSS rescoreEPSS 64% · 99th percentile
- 2026-08-26 14:41 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-25 13:44 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-24 14:10 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-21 23:44 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-20 22:50 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-19 16:59 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-16 02:10 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-15 01:26 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-13 22:34 UTCOSV refresh
- 2026-08-13 21:56 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-08 16:32 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-06 13:42 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-04 10:32 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-30 16:24 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-29 01:17 UTCOSV refresh
- 2026-07-28 15:32 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-26 14:51 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-23 01:26 UTCEG score recompute▲ 1.10
- 2026-07-22 22:05 UTCEG score recompute▼ 1.50
- 2026-07-22 14:04 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-21 15:21 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-20 17:04 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-19 02:26 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-15 16:54 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-13 22:26 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-12 05:43 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-11 17:41 UTCOSV refresh
- 2026-07-11 08:24 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-09 19:06 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-07 13:42 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-06 16:24 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-06 02:20 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-04 06:28 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-06-30 23:19 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-06-28 04:53 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-06-25 13:47 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-06-24 14:02 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-06-23 21:30 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-06-23 00:00 UTCOSV refresh
- 2026-06-21 01:57 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-06-19 19:23 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-06-18 17:50 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-06-17 17:50 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-06-15 17:45 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-06-13 22:57 UTCEPSS rescoreEPSS 91% · 99th percentile
- 2026-06-12 23:09 UTCEPSS rescoreEPSS 91% · 99th percentile
- 2026-06-10 22:15 UTCEPSS rescoreEPSS 91% · 99th percentile
- 2026-06-08 14:14 UTCEPSS rescoreEPSS 91% · 99th percentile
- 2026-06-06 13:45 UTCEPSS rescoreEPSS 91% · 99th percentile
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:7:tomcat7
- CVE-2016-8735EG 9.8 KEVEPSS p100CRITICAL
- CVE-2017-5648EG 9.1EPSS p96CRITICAL
- CVE-2016-5018EG 9.1EPSS p96CRITICAL
- CVE-2016-0714EG 8.8EPSS p96HIGH
- CVE-2015-5351EG 8.8EPSS p95HIGH
- CVE-2015-5346EG 8.1EPSS p96HIGH
- CVE-2016-9775EG 7.8HIGH
- CVE-2016-9774EG 7.8HIGH
- CVE-2016-1240EG 7.8EPSS p96HIGH
- CVE-2016-3092NVD 7.5EG 7.7EPSS p99HIGH
Same vendor
8 shownredhat:RHSA-2018:0465 · ubuntu:USN-3665-1
Frequently asked(5)
What is CVE-2017-12616?
When was CVE-2017-12616 made public?
Is CVE-2017-12616 actively exploited?
What is the CVSS score of CVE-2017-12616?
How do I remediate CVE-2017-12616?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-12616
Is Your Infrastructure Affected by CVE-2017-12616?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.