# CVE-2016-8735: Apache Tomcat Remote Code Execution

> Remote attackers can execute arbitrary code on Apache Tomcat servers if the JmxRemoteLifecycleListener is enabled and JMX ports are accessible.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 12 May 2023 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Apr 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-cw54-59pw-4g8c, UBUNTU-CVE-2016-8735, USN-7242-1

## What is CVE-2016-8735?

CVE-2016-8735 is a critical unsafe deserialization vulnerability in Apache Tomcat, published on 6 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### 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.

## Which versions are affected by CVE-2016-8735?

20 open source packages ship an affected version, including org.apache.tomcat:tomcat-catalina and org.apache.tomcat:tomcat-catalina-jmx-remote. It affects 19 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.tomcat:tomcat-catalina` | Maven | All versions | 6.0.48 |
| `org.apache.tomcat:tomcat-catalina` | Maven | All versions | 6.0.48 |
| `org.apache.tomcat:tomcat-catalina` | Maven | From 7.0.0 | 7.0.73 |
| `org.apache.tomcat:tomcat-catalina` | Maven | From 7.0.0 | 7.0.73 |
| `org.apache.tomcat:tomcat-catalina` | Maven | From 8.0.0 | 8.0.39 |
| `org.apache.tomcat:tomcat-catalina` | Maven | From 8.0.0 | 8.0.39 |
| `org.apache.tomcat:tomcat-catalina` | Maven | From 8.5.0 | 8.5.7 |
| `org.apache.tomcat:tomcat-catalina` | Maven | From 8.5.0 | 8.5.7 |
| `org.apache.tomcat:tomcat-catalina` | Maven | From 9.0.0.M1 | 9.0.0.M12 |
| `org.apache.tomcat:tomcat-catalina` | Maven | From 9.0.0.M1 | 9.0.0.M12 |
| `org.apache.tomcat:tomcat-catalina-jmx-remote` | Maven | All versions | 6.0.48 |
| `org.apache.tomcat:tomcat-catalina-jmx-remote` | Maven | All versions | 6.0.48 |
| `org.apache.tomcat:tomcat-catalina-jmx-remote` | Maven | From 7.0.0 | 7.0.73 |
| `org.apache.tomcat:tomcat-catalina-jmx-remote` | Maven | From 7.0.0 | 7.0.73 |
| `org.apache.tomcat:tomcat-catalina-jmx-remote` | Maven | From 8.0.0 | 8.0.39 |
| `org.apache.tomcat:tomcat-catalina-jmx-remote` | Maven | From 8.0.0 | 8.0.39 |
| `org.apache.tomcat:tomcat-catalina-jmx-remote` | Maven | From 8.5.0 | 8.5.7 |
| `org.apache.tomcat:tomcat-catalina-jmx-remote` | Maven | From 8.5.0 | 8.5.7 |
| `org.apache.tomcat:tomcat-catalina-jmx-remote` | Maven | From 9.0.0.M1 | 9.0.0.M12 |
| `org.apache.tomcat:tomcat-catalina-jmx-remote` | Maven | From 9.0.0.M1 | 9.0.0.M12 |

Products: Apache Tomcat, Canonical Ubuntu Linux, Debian Debian Linux, Netapp 7-Mode Transition Tool, Netapp Oncommand Insight, Netapp Oncommand Shift, Netapp Snap Creator Framework, Oracle Agile Engineering Data Management, Oracle Agile Product Lifecycle Management, Oracle Communications Application Session Controller, Oracle Communications Instant Messaging Server, Oracle Communications Interactive Session Recorder, Oracle Hospitality Guest Access, Oracle Micros Relate Crm Software, Oracle Micros Retail Xbri Loss Prevention, Oracle Mysql Enterprise Monitor, Oracle Retail Convenience and Fuel Pos Software, Oracle Transportation Management, Redhat Jboss Enterprise Web Server.

## How do I fix CVE-2016-8735?

Upgrade org.apache.tomcat:tomcat-catalina to a fixed version for your release line: 6.0.48, 7.0.73, 8.0.39 or 8.5.7. US federal agencies must fix it by 2 Jun 2023.

## Is CVE-2016-8735 being exploited?

Yes. Attackers have exploited CVE-2016-8735 in the wild since at least 12 May 2023.

## Other vulnerabilities in Apache Tomcat

- [CVE-2025-24813](https://insights.sbomify.com/CVE-2025-24813/): Apache Tomcat Path Equivalence (critical 10.0, exploited in the wild)
- [CVE-2017-12617](https://insights.sbomify.com/CVE-2017-12617/): Apache Tomcat Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2017-12615](https://insights.sbomify.com/CVE-2017-12615/): Apache Tomcat on Windows Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2026-34486](https://insights.sbomify.com/CVE-2026-34486/): Apache Tomcat Missing Encryption of Sensitive Data (high 7.5, exploited in the wild)
- [CVE-2026-65637](https://insights.sbomify.com/CVE-2026-65637/): Apache Tomcat: HTTP/2 no-authority bypass of strict SNI validation - CVE-2026-32990 fix incomplete (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-8735 and fix it if it is affected.

What it is: CVE-2016-8735 is a critical unsafe deserialization vulnerability in Apache Tomcat, published on 6 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2016-8735 in the wild since at least 12 May 2023.

Affected packages and fixed versions:
- org.apache.tomcat:tomcat-catalina (Maven): affected all versions; fixed in 6.0.48
- org.apache.tomcat:tomcat-catalina (Maven): affected all versions; fixed in 6.0.48
- org.apache.tomcat:tomcat-catalina (Maven): affected from 7.0.0; fixed in 7.0.73
- org.apache.tomcat:tomcat-catalina (Maven): affected from 7.0.0; fixed in 7.0.73
- org.apache.tomcat:tomcat-catalina (Maven): affected from 8.0.0; fixed in 8.0.39
- org.apache.tomcat:tomcat-catalina (Maven): affected from 8.0.0; fixed in 8.0.39
- org.apache.tomcat:tomcat-catalina (Maven): affected from 8.5.0; fixed in 8.5.7
- org.apache.tomcat:tomcat-catalina (Maven): affected from 8.5.0; fixed in 8.5.7
- org.apache.tomcat:tomcat-catalina (Maven): affected from 9.0.0.M1; fixed in 9.0.0.M12
- org.apache.tomcat:tomcat-catalina (Maven): affected from 9.0.0.M1; fixed in 9.0.0.M12
- org.apache.tomcat:tomcat-catalina-jmx-remote (Maven): affected all versions; fixed in 6.0.48
- org.apache.tomcat:tomcat-catalina-jmx-remote (Maven): affected all versions; fixed in 6.0.48

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-8735/ (Markdown: https://insights.sbomify.com/CVE-2016-8735/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-8735
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-8735
- OSV: https://osv.dev/vulnerability/CVE-2016-8735

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-8735/
Summaries are generated and may contain mistakes; the official description above is the record.
