Is org.apache.tika:tika-core 3.2 vulnerable?
Maven · 4 releases from 3.2.0 to 3.2.3 · latest org.apache.tika:tika-core is 4.2.0 · checked 18 Nov 2026
No known advisories in the last release
org.apache.tika:tika-core 3.2.3, the last 3.2 release, has no known advisories. 1 advisory affects earlier 3.2.x releases, so update to 3.2.3.
mvn versions:use-dep-version -Dincludes=org.apache.tika:tika-core -DdepVersion=3.2.3 -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
Fixed within 3.2.x, affecting earlier releases
Apache Tika has XXE vulnerability
- Affected
- >=1.13 <3.2.2
- Fixed in
- 3.2.2
Every org.apache.tika:tika-core 3.2.x release
Affected: 3.2.0 to 3.2.1. 3.2.2 and later are not affected. Latest org.apache.tika:tika-core: 4.2.0.
| Version | Known advisories |
|---|---|
| org.apache.tika:tika-core 3.2.3 | None |
| org.apache.tika:tika-core 3.2.2 | None |
| org.apache.tika:tika-core 3.2.1 | CVE-2025-66516 |
| org.apache.tika:tika-core 3.2.0 | CVE-2025-66516 |
Which of your client projects are still on org.apache.tika:tika-core 3.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.apache.tika:tika-core version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.apache.tika:tika-core versions
- org.apache.tika:tika-core 4.1
- org.apache.tika:tika-core 4.0
- org.apache.tika:tika-core 3.3
- org.apache.tika:tika-core 3.1
- org.apache.tika:tika-core 3.0
- org.apache.tika:tika-core 2.9
- org.apache.tika:tika-core 4.2
- org.apache.tika:tika-core 2.8
- org.apache.tika:tika-core 2.7
- org.apache.tika:tika-core 2.6
- org.apache.tika:tika-core 2.5
- org.apache.tika:tika-core 2.4
- All org.apache.tika:tika-core advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.