CVE REMEDIATION GUIDE
CISA KEV · Known exploitedCriticalFixed-version data available

CVE-2016-8735 remediation guide

Apache Tomcat

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.

Open CVE record
ProductApache Tomcat
Affected versionsbefore 6.0.48, 7.x before 7.0.73, 8.x before 8.0.39, 8.5.x before 8.5.7, 9.x before 9.0.0.M12, < 6.0.48, >= 7.0.0 < 7.0.73, >= 8.0 < 8.0.39, >= 8.5.0 < 8.5.7, 9.0.0, 16.04, 8.0, 3.0.0, 6.1.3, 6.2.0, 6.2.1.0, 9.3.5, 9.3.6, 3.7.1, 3.8.0
Fixed versions6.0.48, 7.0.73, 8.0.39, 8.5.7
Priority basisImmediate · CVSS 9.8 · EPSS 90.3%
01

Identify the affected asset

Confirm whether Apache Tomcat is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: before 6.0.48, 7.x before 7.0.73, 8.x before 8.0.39, 8.5.x before 8.5.7, 9.x before 9.0.0.M12, < 6.0.48, >= 7.0.0 < 7.0.73, >= 8.0 < 8.0.39, >= 8.5.0 < 8.5.7, 9.0.0, 16.04, 8.0, 3.0.0, 6.1.3, 6.2.0, 6.2.1.0, 9.3.5, 9.3.6, 3.7.1, 3.8.0. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply updates per vendor instructions.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.