org.apache.tika:tika-core vulnerabilities
This is the core Apache Tika™ toolkit library from which all other modules inherit functionality. It also includes the core facades for the Tika API.
- Registry
- Maven
- Latest
- 4.2.0
13 known advisories
The latest version, 4.2.0, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=org.apache.tika:tika-core -DdepVersion=4.2.0 -DforceVersion=trueIs your project on an affected org.apache.tika:tika-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.apache.tika:tika-core
Apache Tika has XXE vulnerability
- Affected
- >=1.13 <3.2.2
- Fixed in
- 3.2.2
Regular expression denial of service in apache tika
- Affected
- >=1.17 <1.28.3
- Fixed in
- 1.28.3
Regular expression denial of service in apache tika
- Affected
- >=1.17 <1.28.2 · >=2.0.0 <2.4.0
- Fixed in
- 1.28.2, 2.4.0
Allocation of Resources Without Limits or Throttling in Apache Tika
- Affected
- >=1.7 <1.22
- Fixed in
- 1.22
Allocation of Resources Without Limits or Throttling in Apache Tika
- Affected
- >=1.7 <1.22
- Fixed in
- 1.22
Moderate severity vulnerability that affects org.apache.tika:tika-core
- Affected
- <1.18
- Fixed in
- 1.18
Comparison errorr in org.apache.tika:tika-core
- Affected
- >=1.2 <1.19
- Fixed in
- 1.19
Moderate severity vulnerability that affects org.apache.tika:tika-core
- Affected
- >=0.9 <1.19
- Fixed in
- 1.19
High severity vulnerability that affects org.apache.tika:tika-core
- Affected
- >=0.1 <1.19.1
- Fixed in
- 1.19.1
Apache Tika allows Java code execution for serialized objects embedded in MATLAB files
- Affected
- <1.14
- Fixed in
- 1.14
Apache Tika does not properly initialize the XML parser or choose handlers
- Affected
- <1.13
- Fixed in
- 1.13
Command injection in org.apache.tika:tika-core
- Affected
- >=1.7 <1.18
- Fixed in
- 1.18
Apache Tika is vulnerable to entity expansions which can lead to a denial of service attack
- Affected
- >=0.1 <1.19.1
- Fixed in
- 1.19.1
Is your org.apache.tika:tika-core version vulnerable?
- org.apache.tika:tika-core 4.2No known advisories in 4.2.0
- org.apache.tika:tika-core 4.1No known advisories in 4.1.0
- org.apache.tika:tika-core 4.0No known advisories in 4.0.0
- org.apache.tika:tika-core 3.3No known advisories in 3.3.3
- org.apache.tika:tika-core 3.2No known advisories in 3.2.3
- org.apache.tika:tika-core 3.11 advisory in 3.1.0
- org.apache.tika:tika-core 3.01 advisory in 3.0.0
- org.apache.tika:tika-core 2.91 advisory in 2.9.4
- org.apache.tika:tika-core 2.81 advisory in 2.8.0
- org.apache.tika:tika-core 2.71 advisory in 2.7.0
- org.apache.tika:tika-core 2.61 advisory in 2.6.0
- org.apache.tika:tika-core 2.51 advisory in 2.5.0
- org.apache.tika:tika-core 2.41 advisory in 2.4.1
Which of your client projects still run an old org.apache.tika:tika-core?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.