CSIRTS // UNIFIED SECURITY ADVISORY FEEDSYS ● ONLINE · POWERED BY INTELFUSIONS.COM

CVE-2016-8735

criticalknown exploitedpublic exploitcovered by 1 sourcefirst seen 2023-05-12
Actively exploited. CVE-2016-8735 is listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-05-12) — exploitation has been observed in the wild, and US federal agencies are required to remediate it under BOD 22-01. Treat patching as urgent.
Public exploit code is available. Proof-of-concept or working exploit code for CVE-2016-8735 is indexed in GitHub PoC. Expect opportunistic scanning and exploitation attempts — prioritize remediation.
Apache Tomcat contains an unspecified vulnerability that allows for remote code execution if JmxRemoteLifecycleListener is used and an attacker can reach Java Management Extension (JMX) ports. This CVE exists because this listener wasn't updated for consistency with the Oracle patched issues for CVE-2016-3427 which affected credential types.

CSIRTS triage

What
There is a vulnerability that allows for remote code execution if JmxRemoteLifecycleListener is used and an attacker can reach JMX ports.
Who is affected
Deployments of Apache Tomcat using JmxRemoteLifecycleListener are affected.
Urgency
Remediation is urgent due to the critical severity and confirmed exploitation.
Action
Users should update to the latest version of Apache Tomcat.

AI-assisted analysis generated from the source advisory — verify against the original.

⚡ Watch CVE-2016-8735

Get an email if CVE-2016-8735 is added to CISA KEV, gains public exploit code, or a new advisory cites it — max one per day, one-click unsubscribe.

Exploitation outlook

Exploit availability

Public exploit or proof-of-concept code for CVE-2016-8735 is indexed in these free datasets. Available exploit code raises real-world risk independent of the CVSS score.

Advisory coverage (1)

External references

NVD record for CVE-2016-8735

CVE.org record

CISA KEV catalog

Embed the live status

CVE-2016-8735 live status badge — this badge updates automatically when the KEV or exploit status changes. How to embed it →

[![CVE-2016-8735 status](https://www.csirts.com/badge/CVE-2016-8735)](https://www.csirts.com/cve/CVE-2016-8735)