Is org.apache.tika:tika-core 2.1 vulnerable?

Maven · 1 release from 2.1.0 to 2.1.0 · latest org.apache.tika:tika-core is 4.2.0 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. org.apache.tika:tika-core 2.1.0, the last 2.1 release, is affected by 2 known security advisories (1 critical, 1 medium), including CVE-2025-66516, CVE-2022-30126. Upgrade to 3.2.2 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=org.apache.tika:tika-core -DdepVersion=3.2.2 -DforceVersion=true

Is your project on an affected org.apache.tika:tika-core?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting org.apache.tika:tika-core 2.1.0

  • CriticalCVE-2025-66516GHSA-f58c-gq56-vjjf4 Dec 2025

    Apache Tika has XXE vulnerability

    Affected
    >=1.13 <3.2.2
    Fixed in
    3.2.2
  • MediumCVE-2022-30126GHSA-rpjm-422r-95mh17 May 2022

    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

Which of your client projects are still on org.apache.tika:tika-core 2.1?

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

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.