Tika vulnerabilitiesRanked by how likely they are to be used.
Tika is made by Apache. We track 24 published vulnerabilities in it, across 67 versions. None of them is on the list of flaws known to be exploited today. If you run Tika, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Tika vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Tika's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Tika flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 94%CVE-2018-1335High
From Apache Tika versions 1.7 to 1.17, clients could send carefully crafted headers to tika-server that could be used to inject commands into the command line of the server running tika-server.
- 49%CVE-2025-54988High
Critical XXE in Apache Tika (tika-parser-pdf-module) in Apache Tika 1.13 through and including 3.2.1 on all platforms allows an attacker to carry out XML External Entity injection via a crafted XFA file inside of a PDF.
- 19%CVE-2021-33813High
An XXE issue in SAXBuilder in JDOM through 2.0.6 allows attackers to cause a denial of service via a crafted HTTP request.
- 9.4%CVE-2018-11761High
In Apache Tika 0.1 to 1.18, the XML parsers were not configured to limit entity expansion.
- 8.0%CVE-2016-6809Critical
Apache Tika before 1.14 allows Java code execution for serialized objects embedded in MATLAB files.
- 7.5%CVE-2018-11796High
In Apache Tika 1.19 (CVE-2018-11761), we added an entity expansion limit for XML parsing.
- 6.5%CVE-2015-3271Medium
Apache Tika server (aka tika-server) in Apache Tika 1.9 might allow remote attackers to read arbitrary files via the HTTP fileUrl header.
- 6.1%CVE-2018-17197Medium
A carefully crafted or corrupt sqlite file can cause an infinite loop in Apache Tika's SQLite3Parser in versions 1.8-1.19.1 of Apache Tika.
- 5.4%CVE-2018-11762Medium
In Apache Tika 0.9 to 1.18, in a rare edge case where a user does not specify an extract directory on the commandline (--extract-dir=) and the input file has an embedded file with an absolute path, such as...
- 4.8%CVE-2019-10088High
A carefully crafted or corrupt zip file can cause an OOM in Apache Tika's RecursiveParserWrapper in versions 1.7-1.21.
Running Tika? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
From Apache Tika versions 1.7 to 1.17, clients could send carefully crafted headers to tika-server that could be used to inject commands into the command line of the server running tika-server. This vulnerability only affects those running tika-server on a server that is open to untrusted clients. The mitigation is to upgrade to Tika 1.18.
- Matched to
- Tika on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 24 published vulnerabilities listed under the name Tika, across 67 versions.
None of Tika's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Tika. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.