CVE-2016-8735

CRITICALNVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2023-05-12), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 3 sources updated this weekExploited in the wild
9.8EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • 5,576 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
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 90%CVSS: 9.8Exploit: cisa kev · ssvc active · epss top5pct · epss highExposed services: 5,576

A fix is available — apply it.

Remote code execution is possible with Apache Tomcat before 6.0.48, 7.x before 7.0.73, 8.x before 8.0.39, 8.5.x before 8.5.7, and 9.x before 9.0.0.M12 if JmxRemoteLifecycleListener is used and an attacker can reach JMX ports. The issue exists because this listener wasn't updated for consistency with the CVE-2016-3427 Oracle patch that affected credential types.

Internet exposure · derived from Shodan data

5,576 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2016-8735, in our KEV-Exposure radar’s Shodan-derived sample.

across 120 countries (China, United States, Korea, Republic of, Germany, Japan)top: tomcat
See the KEV-Exposure radar →Derived from Shodan data. Shodan data is owned by Shodan, which holds its copyright (© Shodan). EchelonGraph claims no ownership of it or copyright in it. Aggregate, host-redacted.

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
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation100% × 40%
Automatability100% × 15%
CISA SSVC: Attend at low mission impact; Act at medium or high.
Action: A fix is available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.
EPSS PROB
90%
EPSS %ILE
99th
KEV
⚠ Exploited

CISA SSVCAttend at low mission impact; Act at medium or high.

A fix is available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 6, 2017

Last Modified

August 25, 2026

Advisory Details (6)

Auto-updated Oct 7, 2026
Patch available.
generic

Apache Tomcat® - Apache Tomcat 9 vulnerabilities

http://tomcat.apache.org/security-9.html
generic

Apache Tomcat® - Apache Tomcat 8 vulnerabilities

http://tomcat.apache.org/security-8.html
generic

Apache Tomcat® - Apache Tomcat 7 vulnerabilities

http://tomcat.apache.org/security-7.html
generic

Apache Tomcat® - Apache Tomcat 6 vulnerabilities

http://tomcat.apache.org/security-6.html
generic

oss-sec: [SECURITY] CVE-2016-8735 Apache Tomcat Remote Code Execution

http://seclists.org/oss-sec/2016/q4/502
generic
http://rhn.redhat.com/errata/RHSA-2017-0457.html

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntutomcat8 (8.0.37-1ubuntu0.1) @ yakkety2026-10-11ubuntu
ubuntutomcat6-user (6.0.39-1ubuntu0.1+esm2) @ trusty2026-10-11ubuntu
ubuntulibservlet2.5-java-doc (6.0.45+dfsg-1ubuntu0.1) @ xenial2026-10-11ubuntu
redhatpatch2017-03-07redhat
redhattomcat-vault-0:1.0.8-9.Final_redhat_2.1.ep7.el72017-03-07redhat
redhattomcat-vault-0:1.0.8-9.Final_redhat_2.1.ep7.el62017-03-07redhat

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

(6 across 3 ecosystems)
Debian:7(2)
PackageVulnerable rangeFix by version rangeDependents
tomcat66.0.35-6 ... 6.0.45-1~deb6u1 (15 versions)
  • every version up to 6.0.45+dfsg-1~deb7u3: fixed in 6.0.45+dfsg-1~deb7u3
—
tomcat77.0.28-4 ... 7.0.28-4+deb7u6 (7 versions)
  • every version up to 7.0.28-4+deb7u7: fixed in 7.0.28-4+deb7u7
—
Debian:8(2)
PackageVulnerable rangeFix by version rangeDependents
tomcat77.0.56-3 ... 7.0.56-3+deb8u5 (6 versions)
  • every version up to 7.0.56-3+deb8u6: fixed in 7.0.56-3+deb8u6
—
tomcat88.0.14-1, 8.0.14-1+deb8u1, 8.0.14-1+deb8u2, 8.0.14-1+deb8u3, 8.0.14-1+deb8u4
  • every version up to 8.0.14-1+deb8u5: fixed in 8.0.14-1+deb8u5
—
Maven(2)
PackageVulnerable rangeFix by version rangeDependents
org.apache.tomcat:tomcat-catalina9.0.0.M1 ... 9.0.0.M9 (8 versions)
  • every version up to 6.0.48: fixed in 6.0.48
  • 7.0.0 up to 7.0.73: fixed in 7.0.73
  • 8.0.0 up to 8.0.39: fixed in 8.0.39
  • 8.5.0 up to 8.5.7: fixed in 8.5.7
  • 9.0.0.M1 up to 9.0.0.M12: fixed in 9.0.0.M12
—
org.apache.tomcat:tomcat-catalina-jmx-remote9.0.0.M1 ... 9.0.0.M9 (8 versions)
  • every version up to 6.0.48: fixed in 6.0.48
  • 7.0.0 up to 7.0.73: fixed in 7.0.73
  • 8.0.0 up to 8.0.39: fixed in 8.0.39
  • 8.5.0 up to 8.5.7: fixed in 8.5.7
  • 9.0.0.M1 up to 9.0.0.M12: fixed in 9.0.0.M12
—

All Vendor Advisories

(6)

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 42× in last 7d / 195× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 878 total refreshes for this CVE.

  1. 2026-10-11 00:13 UTCVendor advisory
  2. 2026-10-10 19:52 UTCVendor advisory
  3. 2026-10-10 15:32 UTCVendor advisory
  4. 2026-10-10 11:11 UTCVendor advisory
  5. 2026-10-10 06:52 UTCVendor advisory
  6. 2026-10-10 02:34 UTCVendor advisory
  7. 2026-10-09 22:15 UTCVendor advisory
  8. 2026-10-09 17:56 UTCVendor advisory
  9. 2026-10-09 13:35 UTCVendor advisory
  10. 2026-10-09 09:16 UTCVendor advisory
  11. 2026-10-09 04:57 UTCVendor advisory
  12. 2026-10-09 00:37 UTCVendor advisory
  13. 2026-10-08 20:19 UTCVendor advisory
  14. 2026-10-08 16:00 UTCVendor advisory
  15. 2026-10-08 11:41 UTCVendor advisory
  16. 2026-10-08 07:22 UTCVendor advisory
  17. 2026-10-08 03:03 UTCEG score recompute
  18. 2026-10-08 03:03 UTCVendor advisory
  19. 2026-10-07 23:40 UTCEPSS rescore
  20. 2026-10-07 22:44 UTCVendor advisory
  21. 2026-10-07 18:25 UTCVendor advisory
  22. 2026-10-07 14:05 UTCVendor advisory
  23. 2026-10-07 09:43 UTCVendor advisory
  24. 2026-10-07 05:24 UTCVendor advisory
  25. 2026-10-07 01:05 UTCVendor advisory
Show 75 more
  1. 2026-10-06 20:46 UTCVendor advisory
  2. 2026-10-06 16:28 UTCVendor advisory
  3. 2026-10-06 12:09 UTCVendor advisory
  4. 2026-10-06 07:50 UTCVendor advisory
  5. 2026-10-06 03:31 UTCVendor advisory
  6. 2026-10-06 03:30 UTCVendor advisory
  7. 2026-10-05 23:11 UTCVendor advisory
  8. 2026-10-05 18:51 UTCVendor advisory
  9. 2026-10-05 14:31 UTCVendor advisory
  10. 2026-10-05 10:13 UTCVendor advisory
  11. 2026-10-05 05:53 UTCVendor advisory
  12. 2026-10-05 01:33 UTCVendor advisory
  13. 2026-10-04 21:14 UTCVendor advisory
  14. 2026-10-04 16:55 UTCVendor advisory
  15. 2026-10-04 12:35 UTCVendor advisory
  16. 2026-10-04 08:16 UTCVendor advisory
  17. 2026-10-04 03:57 UTCVendor advisory
  18. 2026-10-03 23:38 UTCVendor advisory
  19. 2026-10-03 19:18 UTCVendor advisory
  20. 2026-10-03 14:59 UTCEG score recompute
  21. 2026-10-03 14:59 UTCVendor advisory
  22. 2026-10-03 14:21 UTCEPSS rescore
  23. 2026-10-03 14:21 UTCEPSS rescore
  24. 2026-10-03 10:40 UTCVendor advisory
  25. 2026-10-03 06:21 UTCVendor advisory
  26. 2026-10-03 02:02 UTCVendor advisory
  27. 2026-10-02 21:43 UTCVendor advisory
  28. 2026-10-02 17:25 UTCVendor advisory
  29. 2026-10-02 13:04 UTCVendor advisory
  30. 2026-10-02 08:45 UTCVendor advisory
  31. 2026-10-02 04:26 UTCVendor advisory
  32. 2026-10-02 00:04 UTCVendor advisory
  33. 2026-10-01 19:46 UTCVendor advisory
  34. 2026-10-01 15:26 UTCVendor advisory
  35. 2026-10-01 11:08 UTCVendor advisory
  36. 2026-10-01 06:46 UTCVendor advisory
  37. 2026-10-01 02:26 UTCVendor advisory
  38. 2026-09-30 22:08 UTCVendor advisory
  39. 2026-09-30 17:49 UTCVendor advisory
  40. 2026-09-30 13:31 UTCVendor advisory
  41. 2026-09-30 09:11 UTCVendor advisory
  42. 2026-09-30 04:53 UTCVendor advisory
  43. 2026-09-30 00:34 UTCVendor advisory
  44. 2026-09-29 20:13 UTCVendor advisory
  45. 2026-09-29 15:51 UTCVendor advisory
  46. 2026-09-29 11:33 UTCVendor advisory
  47. 2026-09-29 07:14 UTCVendor advisory
  48. 2026-09-29 02:55 UTCVendor advisory
  49. 2026-09-28 22:36 UTCEG score recompute
  50. 2026-09-28 22:36 UTCVendor advisory
  51. 2026-09-28 18:18 UTCVendor advisory
  52. 2026-09-28 13:59 UTCVendor advisory
  53. 2026-09-28 09:40 UTCVendor advisory
  54. 2026-09-28 05:22 UTCVendor advisory
  55. 2026-09-28 01:03 UTCVendor advisory
  56. 2026-09-27 21:51 UTCCISA KEV update
  57. 2026-09-27 20:44 UTCVendor advisory
  58. 2026-09-27 16:25 UTCVendor advisory
  59. 2026-09-27 12:07 UTCVendor advisory
  60. 2026-09-27 07:48 UTCVendor advisory
  61. 2026-09-27 03:29 UTCVendor advisory
  62. 2026-09-26 23:08 UTCVendor advisory
  63. 2026-09-26 18:47 UTCVendor advisory
  64. 2026-09-26 14:28 UTCVendor advisory
  65. 2026-09-26 10:07 UTCVendor advisory
  66. 2026-09-26 05:45 UTCVendor advisory
  67. 2026-09-26 01:24 UTCVendor advisory
  68. 2026-09-25 21:05 UTCVendor advisory
  69. 2026-09-25 19:35 UTCCISA KEV update
  70. 2026-09-25 16:46 UTCVendor advisory
  71. 2026-09-25 14:55 UTCCISA KEV update
  72. 2026-09-25 12:27 UTCVendor advisory
  73. 2026-09-25 08:09 UTCVendor advisory
  74. 2026-09-25 03:50 UTCVendor advisory
  75. 2026-09-24 23:31 UTCVendor advisory

Related CVEs(same product + same vendor)

Frequently asked(6)

What is CVE-2016-8735?
CVE-2016-8735 is a critical vulnerability published on April 6, 2017. Remote code execution is possible with Apache Tomcat before 6.0.48, 7.x before 7.0.73, 8.x before 8.0.39, 8.5.x before 8.5.7, and 9.x before 9.0.0.M12 if JmxRemoteLifecycleListener is used and an attacker can reach JMX ports. The issue exists because this listener wasn't updated for consistency…
When was CVE-2016-8735 disclosed?
CVE-2016-8735 was first published on April 6, 2017, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-8735 actively exploited?
Yes. CISA added CVE-2016-8735 to the Known Exploited Vulnerabilities catalog on May 12, 2023, affecting Apache Tomcat. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2016-8735?
CVE-2016-8735 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2016-8735?
CVE-2016-8735 affects Apache Tomcat. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2016-8735?
A fix for CVE-2016-8735 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-8735

Explore →

Is Your Infrastructure Affected by CVE-2016-8735?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs