# CVE-2016-6797: Incorrect Authorization in Apache Tomcat > A web application can access unauthorized global JNDI resources in Apache Tomcat due to insufficient access control checks in the ResourceLinkFactory implementation. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 10 Aug 2017 - **Updated:** 8 Oct 2026 - **Also known as:** GHSA-q6x7-f33r-3wxx, UBUNTU-CVE-2016-6797 ## What is CVE-2016-6797? CVE-2016-6797 is a high-severity missing authorization vulnerability in Apache Tomcat, published on 10 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The ResourceLinkFactory implementation 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 and 6.0.0 to 6.0.45 did not limit web application access to global JNDI resources to those resources explicitly linked to the web application. Therefore, it was possible for a web application to access any global JNDI resource whether an explicit ResourceLink had been configured or not. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2016-6797? 8 open source packages ship an affected version, including org.apache.tomcat:tomcat. It affects 14 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.tomcat:tomcat` | Maven | From 7.0.0 | 7.0.72 | | `org.apache.tomcat:tomcat` | Maven | From 7.0.0 | 7.0.72 | | `org.apache.tomcat:tomcat` | Maven | From 8.0.0 | 8.0.37 | | `org.apache.tomcat:tomcat` | Maven | From 8.0.0 | 8.0.37 | | `org.apache.tomcat:tomcat` | Maven | From 8.5.0 | 8.5.5 | | `org.apache.tomcat:tomcat` | Maven | From 8.5.0 | 8.5.5 | | `org.apache.tomcat:tomcat` | Maven | From 9.0.0.M1 | 9.0.0.M10 | | `org.apache.tomcat:tomcat` | Maven | From 9.0.0.M1 | 9.0.0.M10 | Products: Apache Tomcat, Canonical Ubuntu Linux, Debian Debian Linux, Netapp Oncommand Insight, Netapp Oncommand Shift, Netapp Snap Creator Framework, Oracle Tekelec Platform Distribution, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation, Redhat Jboss Enterprise Web Server. ## How do I fix CVE-2016-6797? Upgrade org.apache.tomcat:tomcat to a fixed version for your release line: 7.0.72, 8.0.37, 8.5.5 or 9.0.0.M10. ## Is CVE-2016-6797 being exploited? There is no known exploitation of CVE-2016-6797 in the wild and no public exploit code. ## 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-2016-8735](https://insights.sbomify.com/CVE-2016-8735/): Apache Tomcat Remote Code Execution (critical 9.8, 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) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2016-6797 and fix it if it is affected. What it is: CVE-2016-6797 is a high-severity missing authorization vulnerability in Apache Tomcat, published on 10 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2016-6797 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.tomcat:tomcat (Maven): affected from 7.0.0; fixed in 7.0.72 - org.apache.tomcat:tomcat (Maven): affected from 7.0.0; fixed in 7.0.72 - org.apache.tomcat:tomcat (Maven): affected from 8.0.0; fixed in 8.0.37 - org.apache.tomcat:tomcat (Maven): affected from 8.0.0; fixed in 8.0.37 - org.apache.tomcat:tomcat (Maven): affected from 8.5.0; fixed in 8.5.5 - org.apache.tomcat:tomcat (Maven): affected from 8.5.0; fixed in 8.5.5 - org.apache.tomcat:tomcat (Maven): affected from 9.0.0.M1; fixed in 9.0.0.M10 - org.apache.tomcat:tomcat (Maven): affected from 9.0.0.M1; fixed in 9.0.0.M10 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-6797/ (Markdown: https://insights.sbomify.com/CVE-2016-6797/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2016-6797 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-6797 - OSV: https://osv.dev/vulnerability/CVE-2016-6797 --- From sbomify Insights: https://insights.sbomify.com/CVE-2016-6797/ Summaries are generated and may contain mistakes; the official description above is the record.