GHSA-vrmh-37mg-28h3
Severity by source
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/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:N/R:X/V:X/RE:X/U:X
Network vector because tika-server accepts unauthenticated uploads; no integrity or availability impact, only arbitrary file read.
Primary rating from Vendor (CNA).
CVSS VectorVendor
Lifecycle Timeline
3Description PRE-NVD
AnalysisAI
Relative path traversal in Apache Tika's ISA-Tab parser (ISArchiveParser) enables arbitrary local file read against the Tika process. Specifically, the 'Study Assay File Name' field within an ISA-Tab investigation file is processed without adequate path sanitization, allowing traversal outside the intended dataset directory and causing the contents of any file readable by the Tika process to be emitted in the extracted text output. Affected deployments span Apache Tika 1.8 through 3.3.1 and the 4.0.0-alpha-1 preview release, all of which include the vulnerable tika-parser-scientific-module. No public exploit or CISA KEV listing was identified at time of analysis, but the vulnerability was independently reported by two researchers with proposed patches, indicating the issue is reproducible and well-understood.
Technical ContextAI
Apache Tika is a content detection and extraction toolkit widely used in search engines, data pipelines, and content management systems. This vulnerability resides specifically in the tika-parser-scientific-module (org.apache.tika:tika-parser-scientific-module), an optional add-on that handles scientific data formats including ISA-Tab. ISA-Tab is an open tabular format used in life sciences and bioinformatics research to describe investigation/study/assay structures. The ISArchiveParser processes ISA-Tab archives, reading metadata fields such as 'Study Assay File Name' to locate and parse associated data files. Because this field is consumed as a relative file path without normalization or boundary enforcement, a crafted value such as '../../etc/passwd' or '../../../../proc/self/environ' will resolve outside the archive's dataset directory, causing the parser to open and stream the target file's raw contents into Tika's extracted text output. The root cause class is CWE-23 (Relative Path Traversal), a failure to canonicalize user-controlled path components before filesystem operations. No CPE string was provided in the input data, but the affected Maven artifact is org.apache.tika:tika-parser-scientific-module, versions 1.8 through 3.3.1 and 4.0.0-alpha-1.
RemediationAI
The primary remediation is to upgrade to Apache Tika 3.3.2 (stable branch) or 4.0.0-beta-1 (alpha/preview branch), both of which include the fix contributed via PR #2873. Upgrade documentation and downloads are available at https://tika.apache.org/. If an immediate upgrade is not possible, the most effective workaround is to exclude or not deploy the tika-parser-scientific-module JAR, which removes the ISArchiveParser entirely; the trade-off is loss of ISA-Tab and related scientific format parsing capability. Alternatively, if Tika is deployed as tika-server, restrict the set of accepted MIME types to exclude ISA-Tab ('application/isa-tab' or equivalent) via server configuration, preventing the vulnerable parser from being invoked; verify the effective MIME type Tika assigns to ISA-Tab archives in your environment before relying on this control. For deployments where files are processed from a directory, apply strict filesystem permissions to ensure only trusted processes can write to the Tika-monitored input directories, which limits the attacker's ability to plant a malicious ISA-Tab file. Note that tika-server 3.3.2 also tightens defaults by requiring enableUnsecureFeatures=true for the /pipes, /async, and /status endpoints, providing an additional defense-in-depth improvement.
From Apache Tika versions 1.7 to 1.17, clients could send carefully crafted headers to tika-server that could be used to
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
Critical XXE in Apache Tika (tika-parser-pdf-module) in Apache Tika 1.13 through and including 3.2.1 on all platforms al
An XXE issue in SAXBuilder in JDOM through 2.0.6 allows attackers to cause a denial of service via a crafted HTTP reques
Apache Tika before 1.14 allows Java code execution for serialized objects embedded in MATLAB files. Rated critical sever
A carefully crafted or corrupt zip file can cause an OOM in Apache Tika's RecursiveParserWrapper in versions 1.7-1.21. R
Apache Tika before 1.13 does not properly initialize the XML parser or choose handlers, which might allow remote attacke
A carefully crafted package/compressed file that, when unzipped/uncompressed yields the same file (a quine), causes a St
In Apache Tika 1.19 (CVE-2018-11761), we added an entity expansion limit for XML parsing. Rated high severity (CVSS 7.5)
In Apache Tika 0.1 to 1.18, the XML parsers were not configured to limit entity expansion. Rated high severity (CVSS 7.5
The /unpack endpoint in Apache Tika's server component (tika-server 4.0.0-alpha-1) fails to enforce the operator-configu
In Apache Tika 1.19 to 1.21, a carefully crafted 2003ml or 2006ml file could consume all available SAXParsers in the poo
Same weakness CWE-22 – Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-51277