Skip to content
Server Security Center
KEVcritical9.8

CVE-2016-8735: Apache Tomcat Remote Code Execution

Apache Tomcat · listed in the CISA catalog of actively exploited vulnerabilities since 2023-05-12.

CVSS v3.1 (CVE record)
9.8
critical
EPSS (exploit probability, 30 days)
90%
higher than 99.8% of all CVEs
Added to CISA KEV
2023-05-12
US federal due date 2023-06-02
Ubuntu priority
high

CVE-2016-8735 explained

CVE-2016-8735 is a remote code execution flaw in Apache Tomcat when the JmxRemoteLifecycleListener is used and an attacker can reach the JMX ports. The listener was not updated to match the CVE-2016-3427 Oracle patch on credential types. It is listed in CISA's Known Exploited Vulnerabilities catalog, so it has been exploited in practice.

Impact

An unauthenticated remote attacker who can reach the JMX ports can execute code on the Tomcat server. This requires that JmxRemoteLifecycleListener is configured. No user interaction is needed and attack complexity is low. Successful exploitation can fully compromise the confidentiality, integrity and availability of the affected server. Systems that do not use this listener, or whose JMX ports are unreachable, are not exposed to this attack path.

Who is affected

Ubuntu 14.04 LTS: tomcat6 is fixed in 6.0.39-1ubuntu0.1+esm2, available only through Ubuntu Pro (ESM). tomcat7 is fixed in 7.0.52-1ubuntu0.8. Ubuntu 16.04 LTS: tomcat6 is fixed in 6.0.45+dfsg-1ubuntu0.1, tomcat7 in 7.0.68-1ubuntu0.3, and tomcat8 in 8.0.32-1ubuntu1.3. All listed packages have fixed versions. Both releases are end of life.

Written with AI from the data on this page and checked against it automatically.

Official description

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.

CISA required action: Apply updates per vendor instructions.

CISA notes

Upstream versions (CVE record)

From the CVE record published by the vendor or CVE numbering authority.

  • Apache Software Foundation Apache Tomcat
    Affected
    • 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
    Fixed in
    not stated

    Version statement as published by the CNA (free text).

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

What to do

  1. Check whether any Tomcat instance uses JmxRemoteLifecycleListener and whether its JMX ports are reachable.
  2. Update the installed tomcat6, tomcat7 or tomcat8 package to the fixed version for your release.
  3. On Ubuntu 14.04 LTS, enable Ubuntu Pro (ESM) to receive the fixed tomcat6 package.
  4. Restart Tomcat after updating so the fixed code is loaded.
  5. Block JMX ports from untrusted networks with a firewall.
  6. Plan upgrades from Ubuntu 14.04 LTS and 16.04 LTS to a supported release, since both are end of life.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Run on each Ubuntu or Debian server. Replace tomcat6 with the source package from the table above (this CVE affects 3 source packages).

1. Show installed packages built from the source package, with their versions

dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="tomcat6"'

2. Compare each installed version with the fixed version for your release from the table

I=INSTALLED_VERSION; F=FIXED_VERSION   # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac

3. Install the fix

sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="tomcat6"{print $1}')

Services keep running the old code until they are restarted – restart the affected service or check with needrestart.

Rows marked “fix via Ubuntu Pro”: these fixes are only installable with an Ubuntu Pro subscription (ESM). Attach the machine first (sudo pro attach, then sudo pro enable esm-infra esm-apps), then run the commands above.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-284

Questions about CVE-2016-8735

Am I affected if I do not use JMX?
The description states that exploitation requires JmxRemoteLifecycleListener to be in use and the JMX ports to be reachable by the attacker. If neither applies, this path is not exposed, but updating is still advised.
Is this vulnerability exploited in the wild?
Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 2023-05-12, with a US federal due date of 2023-06-02. Known ransomware use is listed as unknown.
Do I need Ubuntu Pro for the fix?
Only for tomcat6 on Ubuntu 14.04 LTS. All other listed fixes are in the standard archive.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.