How severe is CVE-2016-6794?

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

Which packages are affected by CVE-2016-6794?

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

How do I fix CVE-2016-6794?

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

How do I detect CVE-2016-6794 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-6794 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2016-6794?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2016-6794 can be triaged on real exposure rather than presence alone.

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

No public exploit code has been indexed for CVE-2016-6794 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-6794?

CVE-2016-6794 has an EPSS (Exploit Prediction Scoring System) score of 7.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.

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

CVE-2016-6794 was published on August 10, 2017 and was last updated on July 8, 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-6794 — tomcat

MEDIUMFix: apache/tomcat@0b41766

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

System Property Disclosure in Apache Tomcat

Also known asGHSA-2rvf-329f-p99g

Published

Aug 10, 2017

Updated

Jul 8, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

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

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2016-6794 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

5 pkgs affected

☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕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

When a SecurityManager is configured, a web application's ability to read system properties should be controlled by the SecurityManager. In Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70, 6.0.0 to 6.0.45 the system property replacement feature for configuration files could be used by a malicious web application to bypass the SecurityManager and read system properties that should not be visible.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 6.0.0&&< 6.0.47	6.0.47`org.apache.tomcat:tomcat:6.0.47`
☕Maven	`org.apache.tomcat:tomcat`	≥ 7.0.0&&< 7.0.72	7.0.72`org.apache.tomcat:tomcat:7.0.72`
☕Maven	`org.apache.tomcat:tomcat`	≥ 8.0.0&&< 8.0.37	8.0.37`org.apache.tomcat:tomcat:8.0.37`
☕Maven	`org.apache.tomcat:tomcat`	≥ 8.1.0&&< 8.5.5	8.5.5`org.apache.tomcat:tomcat:8.5.5`
☕Maven	`org.apache.tomcat:tomcat`	≥ 9.0.0.M1&&< 9.0.0.M10	9.0.0.M10`org.apache.tomcat:tomcat:9.0.0.M10`

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 6.0.47 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-6794 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2016-6794 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2016-6794. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 7	`tomcat-0:7.0.76-2.el7`	RHSA-2017:2247
Red Hat JBoss Web Server 3.1	see advisory	RHSA-2017:0457
Red Hat JBoss Web Server 3 for RHEL 6	`hibernate4-eap6-0:4.2.23-1.Final_redhat_1.1.ep6.el6`	RHSA-2017:0455
Red Hat JBoss Web Server 3 for RHEL 7	`hibernate4-eap6-0:4.2.23-1.Final_redhat_1.1.ep6.el7`	RHSA-2017:0456

UbuntuMEDIUM

USN-3177-1Ubuntu USN-4557-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-6794 in your dependencies?

O3 Security finds CVE-2016-6794 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works