NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2016-6796 — tomcat

HIGHFix: apache/tomcat@f603f2f

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

Apache Tomcat vulnerable to SecurityManager bypass

Also known asGHSA-3mjp-p938-4329
Published
Updated
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • 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-6796.

EPSS Exploitation Probability

via FIRST.org ↗
8.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk
0.00%3.52%7.04%10.6%0.8%8.3%May 26Sep 26Nov 26

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

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

A malicious web application running on 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 and 6.0.0 to 6.0.45 was able to bypass a configured SecurityManager via manipulation of the configuration parameters for the JSP Servlet.

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.tomcat:tomcat≥ 9.0.0.M1&&< 9.0.0.M109.0.0.M10org.apache.tomcat:tomcat:9.0.0.M10
☕Mavenorg.apache.tomcat:tomcat≥ 8.5.0&&< 8.5.58.5.5org.apache.tomcat:tomcat:8.5.5
☕Mavenorg.apache.tomcat:tomcat≥ 8.0.0.RC1&&< 8.0.378.0.37org.apache.tomcat:tomcat:8.0.37
☕Mavenorg.apache.tomcat:tomcat≥ 7.0.0&&< 7.0.717.0.71org.apache.tomcat:tomcat:7.0.71
☕Mavenorg.apache.tomcat:tomcat≥ 6.0.0&&< 6.0.466.0.46org.apache.tomcat:tomcat:6.0.46

Affected Products

15 products · 34 configurations
Application
tomcatapache
≥ 8.5.0 && ≤ 8.5.4
1 version
9.0.0
OS
ubuntu linuxcanonical
1 version
16.04
OS
debian linuxdebian
1 version
8.0
Application
oncommand insightnetapp
all
Application
oncommand shiftnetapp
all
Application
snap creator frameworknetapp
all

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

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

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

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
ProductFixed inAdvisory
Red Hat Enterprise Linux 7tomcat-0:7.0.76-2.el7RHSA-2017:2247
Red Hat JBoss Enterprise Application Platform 6.4see advisoryRHSA-2017:1551
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 5hornetq-0:2.3.25-21.SP19_redhat_1.1.ep6.el5RHSA-2017:1550
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6hornetq-0:2.3.25-21.SP19_redhat_1.1.ep6.el6RHSA-2017:1549
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6jboss-ec2-eap-0:7.5.16-1.Final_redhat_1.ep6.el6RHSA-2017:1552
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 7hornetq-0:2.3.25-21.SP19_redhat_1.1.ep6.el7RHSA-2017:1548
Red Hat JBoss Web Server 3.1see advisoryRHSA-2017:0457
Red Hat JBoss Web Server 3 for RHEL 6hibernate4-eap6-0:4.2.23-1.Final_redhat_1.1.ep6.el6RHSA-2017:0455

Frequently Asked Questions

A malicious web application running on 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 and 6.0.0 to 6.0.45 was able to bypass a configured SecurityManager via manipulation of the configuration parameters for the JSP Servlet.
O3 Security · Impact-Aware SCA

Is CVE-2016-6796 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2016-6796: tomcat — Fixed in 9.0.0.M10