Skip to main content

Apache Tika CVE-2026-66756

| EUVDEUVD-2026-51279 MEDIUM
Improper Protection of Alternate Path (CWE-424)
6.9
CVSS 4.0 · Vendor
Share

Severity by source

Vendor (CNA) PRIMARY
6.9 MEDIUM
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
vuln.today AI
7.3 HIGH

Network-accessible REST service with no built-in auth (PR:N, AV:N); impact scoped to Tika server processing with low C/I/A as the bypass enables restricted endpoint access but not direct system compromise.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (CNA).

CVSS VectorVendor

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
X

Lifecycle Timeline

3
Patch available
Jul 30, 2026 - 20:03 EUVD
Analysis Generated
Jul 30, 2026 - 18:16 vuln.today
CVE Published
Jul 30, 2026 - 17:56 oss-security
CRITICAL

Description PRE-NVD

Disclosed via oss-security. NVD scoring and full description are pending.

AnalysisAI

The /unpack endpoint in Apache Tika's server component (tika-server 4.0.0-alpha-1) fails to enforce the operator-configured enableUnsecureFeatures=false security control, classified as Improper Protection of Alternate Path. This means the /unpack endpoint remains fully operational even when administrators have explicitly disabled unsafe features, bypassing the intended security boundary and allowing archive extraction or untrusted content processing through a restricted interface. No public exploit code has been identified and the vulnerability is confined to a pre-production alpha release, significantly limiting real-world exposure.

Technical ContextAI

Apache Tika is a content analysis toolkit that exposes document parsing and extraction capabilities via a REST API through tika-server (org.apache.tika:tika-server). The server includes a security flag, enableUnsecureFeatures (also expressed as unsecureFeatures), that gates access to potentially dangerous endpoints - including /pipes, /async, /status, and now confirmed /unpack - which can expose the service to risks such as resource exhaustion, SSRF, zip-slip path traversal, or triggering parser exploits on attacker-controlled content. The root cause is CWE-424 (Improper Protection of Alternate Path): the /unpack endpoint contains a code path that does not check the enableUnsecureFeatures flag, so the flag's intended restriction is silently bypassed. Context from the contemporaneous Tika 3.3.2 release confirms this pattern - that release backported analogous tightening for /pipes, /async, and /status to the stable 3.x branch, indicating /unpack was identified as requiring the same treatment in the 4.x alpha series.

RemediationAI

Upgrade to Apache Tika 4.0.0-beta-1 or a later release, which contains the fix for the /unpack endpoint authorization bypass; this release is available from the Apache Tika download page at https://tika.apache.org/. Since 4.0.0-alpha-1 is pre-production alpha software, any deployment in a non-experimental context should be treated as a misconfiguration regardless of this CVE, and migration to a stable or beta release is warranted on those grounds alone. As a compensating control before patching, restrict network access to the tika-server process using host-based firewall rules or a reverse proxy with strict ACLs so that only explicitly trusted clients or internal services can reach any tika-server endpoint; this limits the blast radius of the /unpack bypass and aligns with tika-server's intended deployment model of internal-only exposure. Note that restricting the /unpack path specifically at the proxy layer is a targeted option, though it may break legitimate workflows that rely on the endpoint.

More in Tika

View all
CVE-2018-1335 HIGH POC
8.1 Apr 25

From Apache Tika versions 1.7 to 1.17, clients could send carefully crafted headers to tika-server that could be used to

CVE-2025-66516 HIGH POC
8.4 Dec 04

Critical XXE in Apache Tika tika-core (1.13-3.2.1), tika-pdf-module (2.0.0-3.2.1) and tika-parsers (1.13-1.28.5) modules

CVE-2025-54988 HIGH POC
8.4 Aug 20

Critical XXE in Apache Tika (tika-parser-pdf-module) in Apache Tika 1.13 through and including 3.2.1 on all platforms al

CVE-2021-33813 HIGH POC
7.5 Jun 16

An XXE issue in SAXBuilder in JDOM through 2.0.6 allows attackers to cause a denial of service via a crafted HTTP reques

CVE-2016-6809 CRITICAL
9.8 Apr 06

Apache Tika before 1.14 allows Java code execution for serialized objects embedded in MATLAB files. Rated critical sever

CVE-2019-10088 HIGH
8.8 Aug 02

A carefully crafted or corrupt zip file can cause an OOM in Apache Tika's RecursiveParserWrapper in versions 1.7-1.21. R

CVE-2016-4434 HIGH
7.8 Sep 30

Apache Tika before 1.13 does not properly initialize the XML parser or choose handlers, which might allow remote attacke

CVE-2019-10094 HIGH
7.8 Aug 02

A carefully crafted package/compressed file that, when unzipped/uncompressed yields the same file (a quine), causes a St

CVE-2018-11796 HIGH
7.5 Oct 09

In Apache Tika 1.19 (CVE-2018-11761), we added an entity expansion limit for XML parsing. Rated high severity (CVSS 7.5)

CVE-2018-11761 HIGH
7.5 Sep 19

In Apache Tika 0.1 to 1.18, the XML parsers were not configured to limit entity expansion. Rated high severity (CVSS 7.5

CVE-2019-10093 MEDIUM
6.5 Aug 02

In Apache Tika 1.19 to 1.21, a carefully crafted 2003ml or 2006ml file could consume all available SAXParsers in the poo

CVE-2018-17197 MEDIUM
6.5 Dec 24

A carefully crafted or corrupt sqlite file can cause an infinite loop in Apache Tika's SQLite3Parser in versions 1.8-1.1

Share

CVE-2026-66756 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy