# CVE-2018-1305: Apache Tomcat information exposure vulnerability

> Attackers can access unauthorized resources because security constraints were not applied before Servlets loaded, exposing data to unprivileged users.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Feb 2018
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-jx6h-3fjx-cgv5, UBUNTU-CVE-2018-1305

## What is CVE-2018-1305?

CVE-2018-1305 is a medium-severity missing authorization vulnerability in Apache Tomcat, published on 23 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Security constraints defined by annotations of Servlets in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 were only applied once a Servlet had been loaded. Because security constraints defined in this way apply to the URL pattern and any URLs below that point, it was possible - depending on the order Servlets were loaded - for some security constraints not to be applied. This could have exposed resources to users who were not authorised to access them.

## Which versions are affected by CVE-2018-1305?

6 open source packages ship an affected version, including org.apache.tomcat.embed:tomcat-embed-core. It affects 6 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 7.0.0 | 7.0.85 |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 7.0.0 | 7.0.85 |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.0 | 8.5.28 |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.0 | 8.5.28 |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0M1 | 9.0.5 |
| `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0M1 | 9.0.5 |

Products: Apache Tomcat, Canonical Ubuntu Linux, Debian Debian Linux, Oracle Fusion Middleware, Oracle Managed File Transfer, Oracle Micros Relate Crm Software.

## How do I fix CVE-2018-1305?

Upgrade org.apache.tomcat.embed:tomcat-embed-core to a fixed version for your release line: 7.0.85, 8.5.28 or 9.0.5.

## Is CVE-2018-1305 being exploited?

There is no known exploitation of CVE-2018-1305 in the wild and no public exploit code.

Public exploit code:

- Apache Tomcat 安全绕过漏洞 Poc (github_poc): https://github.com/Pa55w0rd/CVE-2018-1305

## 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-2018-1305 and fix it if it is affected.

What it is: CVE-2018-1305 is a medium-severity missing authorization vulnerability in Apache Tomcat, published on 23 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1305 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 7.0.0; fixed in 7.0.85
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 7.0.0; fixed in 7.0.85
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.0; fixed in 8.5.28
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.0; fixed in 8.5.28
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0M1; fixed in 9.0.5
- org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0M1; fixed in 9.0.5

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-2018-1305/ (Markdown: https://insights.sbomify.com/CVE-2018-1305/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1305
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1305
- OSV: https://osv.dev/vulnerability/CVE-2018-1305

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1305/
Summaries are generated and may contain mistakes; the official description above is the record.