CVE-2025-54988: 
Java vulnerability analysis and mitigation

CVE-2025-54988 is a critical XML External Entity (XXE) injection vulnerability in Apache Tika's PDF parser module (tika-parser-pdf-module), affecting versions 1.13 through 3.2.1 on all platforms. The flaw allows an attacker to perform XXE injection via a crafted XFA file embedded inside a PDF, potentially enabling sensitive data disclosure or malicious requests to internal or third-party servers. It was disclosed on August 20, 2025, by Tim Allison of the Apache Tika project, with credit to Paras Jain and Yakov Shafranovich of Amazon as reporters. The vulnerability carries a CVSS v3.1 base score of 8.4 (High) (oss-security, Apache Mailing List, Red Hat).

The vulnerability is classified as CWE-611 (Improper Restriction of XML External Entity Reference). The root cause lies in Apache Tika's PDFParser failing to properly restrict XML external entity processing when parsing XFA (XML Forms Architecture) content embedded within PDF files. An attacker can craft a malicious PDF containing an XFA payload with external entity declarations that, when processed by Tika, cause the XML parser to resolve external references — enabling file reads or server-side request forgery (SSRF). The vulnerability requires no authentication or user interaction and has no privilege prerequisites. The affected module (tika-parser-pdf-module) is a transitive dependency in several widely-used Tika packages including tika-parsers-standard-modules, tika-parsers-standard-package, tika-app, tika-grpc, and tika-server-standard, significantly broadening the attack surface (oss-security, Feedly). Public PoC exploits are available on GitHub (PoC 1, PoC 2).

Successful exploitation allows an attacker to read arbitrary sensitive files from the server's file system (e.g., /etc/passwd, application configuration files, credentials) and trigger unauthorized HTTP requests to internal network resources or external servers (SSRF). The CVSS score reflects high confidentiality, integrity, and availability impacts. Downstream products incorporating Tika as a dependency — including Elasticsearch, Elastic Enterprise Search, IBM SPSS Modeler, HCL Notes, Atlassian products, and FortiGuard-affected systems — are also exposed, making the blast radius substantial across enterprise environments (oss-security, Elastic Advisory, IBM Advisory).

Multiple public proof-of-concept exploits are available on GitHub, added as early as October 2025 (PoC 1, PoC 2). As of the latest available intelligence, there is no confirmed evidence of in-the-wild exploitation, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The EPSS score is approximately 0.025% (0.000250), indicating a currently low but non-negligible probability of exploitation in the near term. No specific threat actor attribution has been reported (Feedly).

1. Reconnaissance: Identify services that use Apache Tika versions 1.13–3.2.1 for document parsing, including Tika server endpoints, Elasticsearch/Enterprise Search instances, or custom applications that accept PDF uploads.
2. Craft malicious PDF: Create a PDF file containing an embedded XFA (XML Forms Architecture) stream with a malicious XXE payload, such as:

   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE foo [
     <!ENTITY xxe SYSTEM "file:///etc/passwd">
   ]>
   <xfa:datasets xmlns:xfa="http://www.xfa.org/schema/xfa-data/1.0/">
     <xfa:data>&xxe;</xfa:data>
   </xfa:datasets>

3. Submit the PDF: Upload or submit the crafted PDF to any endpoint that triggers Tika parsing (e.g., a Tika server REST API endpoint like PUT /tika, a document ingestion pipeline, or a file upload feature backed by Tika).
4. Trigger XXE resolution: When Tika's PDFParser processes the XFA content, the XML parser resolves the external entity, reading the target file or making an outbound HTTP request.
5. Exfiltrate data: The resolved entity content (e.g., file contents) is returned in the parsed metadata or response, or an SSRF request is made to an internal resource, enabling further lateral movement or data exfiltration (oss-security, GitHub PoC).

• Network: Unexpected outbound HTTP/HTTPS requests from Tika server processes to internal IP ranges or external attacker-controlled servers; DNS lookups for attacker-controlled domains originating from the Tika host.
• File System: Unusual access patterns to sensitive files (e.g., /etc/passwd, /etc/shadow, application config files) by the Tika service account as recorded in OS audit logs.
• Logs: Tika server access logs showing PDF file submissions followed by anomalous response content containing file data; Java exception stack traces referencing XFA or XML external entity resolution errors in Tika application logs.
• Process: Unexpected network connections initiated by the Java process running Tika (e.g., java process making outbound connections to non-standard hosts or internal services not normally contacted).
• Application: Repeated submission of PDF files with embedded XFA streams to document parsing endpoints, especially from untrusted or external sources.

The primary remediation is to upgrade Apache Tika to version 3.2.2 or later, which resolves the XXE vulnerability in the PDF parser module (oss-security, Apache Mailing List). For downstream products, apply the following vendor-specific patches:

• Elasticsearch: Upgrade to 8.18.6, 8.19.3, 9.0.6, or 9.1.3 (Elastic Advisory)
• Elastic Enterprise Search: Upgrade to 8.18.6 or 8.19.3 (Elastic Advisory)
• IBM SPSS Modeler: Apply IBM's security bulletin patch (IBM Advisory)

As a temporary workaround where upgrading is not immediately possible, disable XXE processing in XML parsers at the application level and implement strict input validation to reject or sandbox PDF files with embedded XFA content. Restrict network egress from Tika server processes to limit SSRF impact.

The vulnerability received broad coverage from security media outlets including GBHackers, CyberSecurityNews, SecurityOnline, The Hacker News, and The Register, with many highlighting the wide dependency chain of tika-parser-pdf-module as a key concern. Security researcher Kevin Beaumont (GossiTheDog) commented on the vulnerability via Mastodon. The CVE appeared in multiple weekly trending CVE lists on Reddit's r/CVEWatch. CSO Online and InfoWorld noted the vulnerability's significance given Tika's widespread use in enterprise document processing pipelines. The Belgian Centre for Cybersecurity (CCB) issued a warning advisory, and INCIBE-CERT (Spain) also published an alert (GBHackers, The Hacker News, CSO Online).