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 — 4 sources updated this weekExploited in the wild
9.8EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • 7,283 internet-exposed hosts are running an affected version right now
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 90%CVSS: 9.8Exploit: cisa kev · ssvc active · epss top5pct · epss highExposed: 7,283

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.

Live · internet exposure

7,283 internet-exposed hosts are running an affected version of CVE-2016-8735 right now.

across 128 countries (China, United States, Korea, Republic of, Germany, Japan)top: tomcat
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
99(Act)
EG Risk 99/100SSVC: Act

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%
Action: Fix now — active exploitation, automatable, high impact.
EPSS PROB
90%
EPSS %ILE
100%
KEV
⚠ Exploited

Published

April 6, 2017

Last Modified

August 25, 2026

Advisory Details (6)

Auto-updated Aug 25, 2026
No patch confirmed yet.
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 / EcosystemFixed in / PatchReleasedSource
ubuntutomcat8 (8.0.37-1ubuntu0.1) @ yakkety2026-08-26ubuntu
ubuntutomcat6-user (6.0.39-1ubuntu0.1+esm2) @ trusty2026-08-26ubuntu
ubuntulibservlet2.5-java-doc (6.0.45+dfsg-1ubuntu0.1) @ xenial2026-08-26ubuntu
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 rangeFixed inDependents
tomcat66.0.35-6 ... 6.0.45-1~deb6u1 (15 versions)6.0.45+dfsg-1~deb7u3—
tomcat77.0.28-4 ... 7.0.28-4+deb7u6 (7 versions)7.0.28-4+deb7u7—
Debian:8(2)
PackageVulnerable rangeFixed inDependents
tomcat77.0.56-3 ... 7.0.56-3+deb8u5 (6 versions)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+deb8u48.0.14-1+deb8u5—
Maven(2)
PackageVulnerable rangeFixed inDependents
org.apache.tomcat:tomcat-catalina9.0.0.M1 ... 9.0.0.M9 (8 versions)9.0.0.M12—
org.apache.tomcat:tomcat-catalina-jmx-remote9.0.0.M1 ... 9.0.0.M9 (8 versions)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 47× in last 7d / 203× 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 582 total refreshes for this CVE.

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

Related CVEs(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 in the National Vulnerability Database 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 patching attention.
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 full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2016-8735?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-8735, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs