CVE-2015-3271: Exposure of Sensitive Information in org.apache.tika:tika-core

org.apache.tika:tika-server Updated 02 Oct 2025

Summary

17/10/2018
Yes i
Moderate
5.3

CVE-2015-3271: Apache Tika Server exposes sensitive information. Affects org.apache.tika:tika-server versions < 1.10. Fixed in 1.10. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The org.apache.tika:tika-core package is a part of Apache Tika, a content analysis toolkit used for detecting and extracting metadata and structured text content from various file formats. It provides a server component called Apache Tika server (tika-server) that allows users to interact with Tika functionality over HTTP. This vulnerability affects Apache Tika version 1.9. The package is written in Java and is commonly used in Maven-based projects.

Vulnerability Detail

The vulnerability identified as CVE-2015-3271 allows remote attackers to read arbitrary files through the HTTP fileUrl header in Apache Tika server. This means that an attacker can exploit this vulnerability to access sensitive information stored on the server by specifying a malicious file URL. The impact of this vulnerability can be significant as it can lead to unauthorized disclosure of sensitive data.

How To Fix

Latest published version: 4.1.0 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.10

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. The recommended approach is to upgrade to a fixed version of Apache Tika.

Conclusion

The exposure of sensitive information vulnerability in org.apache.tika:tika-core can be mitigated by upgrading to Apache Tika version 1.10 or later. This ensures that the server is protected against remote attackers attempting to read arbitrary files. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for org.apache.tika:tika-server →

Share this vulnerability

FAQ

Apache Tika is a content analysis toolkit used for detecting and extracting metadata and structured text content from various file formats.

The vulnerability allows remote attackers to read arbitrary files, potentially leading to unauthorized disclosure of sensitive information.

To fix this vulnerability, it is recommended to upgrade to Apache Tika version 1.10 or later.

There is no specific workaround mentioned for this vulnerability. The recommended approach is to upgrade to a fixed version of Apache Tika.

For more information about this vulnerability, you can refer to the CVE-2015-3271 entry or contact the Apache Tika project.

How To Fix

Latest published version: 4.1.0 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.10

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback