How severe is CVE-2016-0706?

CVE-2016-0706 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2016-0706?

CVE-2016-0706 affects the following packages: org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven). Ecosystems affected: Maven.

How do I fix CVE-2016-0706?

Update org.apache.tomcat:tomcat to 9.0.0.M2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-0706 is resolved across your whole dependency graph.

How do I detect CVE-2016-0706 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2016-0706 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2016-0706 actively exploited in the wild?

No public exploit code has been indexed for CVE-2016-0706 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2016-0706?

CVE-2016-0706 has an EPSS (Exploit Prediction Scoring System) score of 6.2%, placing it in the 94th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2016-0706?

CVE-2016-0706 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2016-0706 published, and has it been updated?

CVE-2016-0706 was published on February 25, 2016 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2016-0706 — tomcat

MEDIUM

CVE-2016-0706 is a medium-severity (CVSS 4.3) Information Exposure vulnerability in org.apache.tomcat:tomcat. A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat

Also known asGHSA-6vx3-hr43-cfrh

Published

Feb 25, 2016

Updated

Oct 24, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2016-0706.

EPSS Exploitation Probability

via FIRST.org ↗

6.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Apache Tomcat 6.x before 6.0.45, 7.x before 7.0.68, 8.x before 8.0.31, and 9.x before 9.0.0.M2 does not place org.apache.catalina.manager.StatusManagerServlet on the org/apache/catalina/core/RestrictedServlets.properties list, which allows remote authenticated users to bypass intended SecurityManager restrictions and read arbitrary HTTP requests, and consequently discover session ID values, via a crafted web application.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 9.0.0.M1&&< 9.0.0.M2	9.0.0.M2`org.apache.tomcat:tomcat:9.0.0.M2`
☕Maven	`org.apache.tomcat:tomcat`	≥ 8.0.0.RC1&&< 8.0.31	8.0.31`org.apache.tomcat:tomcat:8.0.31`
☕Maven	`org.apache.tomcat:tomcat`	≥ 6.0.0&&< 6.0.45	6.0.45`org.apache.tomcat:tomcat:6.0.45`

Affected Products

3 products · 104 configurations

Application

tomcatapache

90 versions

6.0.06.0.16.0.26.0.46.0.106.0.116.0.136.0.146.0.166.0.186.0.206.0.24

ubuntu linuxcanonical

4 versions

12.0414.0415.1016.04

debian linuxdebian

2 versions

7.08.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tomcat:tomcat to 9.0.0.M2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-0706 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

Product	Fixed in	Advisory
Red Hat Enterprise Linux 6	`tomcat6-0:6.0.24-98.el6_8`	RHSA-2016:2045
Red Hat Enterprise Linux 7	`tomcat-0:7.0.69-10.el7`	RHSA-2016:2599
Red Hat JBoss Enterprise Web Server 2 for RHEL 6	`tomcat7-0:7.0.54-23_patch_05.ep6.el6`	RHSA-2016:2807
Red Hat JBoss Web Server 2.1	`tomcat7`	RHSA-2016:2808
Red Hat JBoss Web Server 3.0	see advisory	RHSA-2016:1089
Red Hat JBoss Web Server 3 for RHEL 6	`httpd24-0:2.4.6-61.ep7.el6`	RHSA-2016:1087
Red Hat JBoss Web Server 3 for RHEL 7	`httpd24-0:2.4.6-61.ep7.el7`	RHSA-2016:1088

UbuntuMEDIUM

USN-3024-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-0706 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works