# CVE-2015-3271: Apache Tika Server exposes sensitive information

> Remote attackers can read arbitrary files from the server via the HTTP fileUrl header in Apache Tika server.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 15 Dec 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-ccjp-w723-2jf2

## What is CVE-2015-3271?

CVE-2015-3271 is a medium-severity path traversal vulnerability in n/a, published on 15 Dec 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Apache Tika server (aka tika-server) in Apache Tika 1.9 might allow remote attackers to read arbitrary files via the HTTP fileUrl header.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2015-3271?

2 open source packages ship an affected version, including org.apache.tika:tika-server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.tika:tika-server` | Maven | All versions | 1.10 |
| `org.apache.tika:tika-server` | Maven | All versions | 1.10 |

Products: Apache Tika.

## How do I fix CVE-2015-3271?

Upgrade org.apache.tika:tika-server to 1.10 or later.

## Is CVE-2015-3271 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-10088](https://insights.sbomify.com/CVE-2019-10088/): Allocation of Resources Without Limits or Throttling in Apache Tika (high 8.8)
- [CVE-2025-66516](https://insights.sbomify.com/CVE-2025-66516/): Apache Tika has XXE vulnerability (high 8.4)
- [CVE-2025-54988](https://insights.sbomify.com/CVE-2025-54988/): Apache Tika PDF parser module: XXE vulnerability in PDFParser's handling of XFA (high 8.4)
- [CVE-2018-1335](https://insights.sbomify.com/CVE-2018-1335/): Command injection in org.apache.tika:tika-core (high 8.1)
- [CVE-2019-10094](https://insights.sbomify.com/CVE-2019-10094/): Allocation of Resources Without Limits or Throttling in Apache Tika (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3271 and fix it if it is affected.

What it is: CVE-2015-3271 is a medium-severity path traversal vulnerability in n/a, published on 15 Dec 2016. 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-2015-3271 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.tika:tika-server (Maven): affected all versions; fixed in 1.10
- org.apache.tika:tika-server (Maven): affected all versions; fixed in 1.10

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

## Sources

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

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