Skip to main content
VulnerabilityPublished Updated

CVE-2026-66756: Apache Tika · Improper Protection of Alternate Path Vulnerability

Affects tikaSource GCVE Database

0
Compare
Authoritative record:CVE-2026-66756· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium · fixed in 4.0.0 : update tika when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.apache.tika/tika-corepkg:maven/org.apache.tika/tika-coreOther threatsAffected–Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Apache Tika to version 4.0.0-beta-1 or later, where this vulnerability is fixed. No other mitigations are specified. Patch status is confirmed by the vendor advisory stating the fix is in 4.0.0-beta-1.

Description

CVE-2026-66756 is an Improper Protection of Alternate Path vulnerability in Apache Tika affecting versions from 4.0.0-alpha-1 up to but not including 4.0.0-beta-1. This vulnerability allows unauthorized access or manipulation due to insufficient protection of alternate file paths. The issue is resolved in version 4.0.0-beta-1, which users are advised to upgrade to.

References

Community reviews

Loading reviews…