How severe is GHSA-f58c-gq56-vjjf?

No CVSS score has been assigned to GHSA-f58c-gq56-vjjf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f58c-gq56-vjjf?

GHSA-f58c-gq56-vjjf affects the following packages: org.apache.tika:tika-core (Maven), org.apache.tika:tika-parsers (Maven), org.apache.tika:tika-parser-pdf-module (Maven). Ecosystems affected: Maven.

How do I fix GHSA-f58c-gq56-vjjf?

Update org.apache.tika:tika-core to 3.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f58c-gq56-vjjf is resolved across your whole dependency graph.

How do I detect GHSA-f58c-gq56-vjjf in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tika:tika-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-f58c-gq56-vjjf if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-f58c-gq56-vjjf?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f58c-gq56-vjjf can be triaged on real exposure rather than presence alone.

Is GHSA-f58c-gq56-vjjf actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-f58c-gq56-vjjf, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-f58c-gq56-vjjf?

GHSA-f58c-gq56-vjjf has an EPSS (Exploit Prediction Scoring System) score of 87.7%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-f58c-gq56-vjjf?

GHSA-f58c-gq56-vjjf is classified as XML External Entity (XXE) (CWE-611). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-f58c-gq56-vjjf?

A Nuclei detection template exists for GHSA-f58c-gq56-vjjf, meaning automated scanners can fingerprint it. 2 Metasploit modules reference GHSA-f58c-gq56-vjjf, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-f58c-gq56-vjjf published, and has it been updated?

GHSA-f58c-gq56-vjjf was published on December 4, 2025 and was last updated on December 5, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

GHSA-f58c-gq56-vjjf — tika-core

GHSA-f58c-gq56-vjjf is a XML External Entity (XXE) vulnerability in org.apache.tika:tika-core. 2 public exploit references exist, so weaponization risk is real. A fix is available for org.apache.tika:tika-core — see the affected versions and patch details below.

Apache Tika has XXE vulnerability

Also known asCVE-2025-66516

Published

Dec 4, 2025

Updated

Dec 5, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

2 known

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-f58c-gq56-vjjf.

EPSS Exploitation Probability

via FIRST.org ↗

87.7%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

3 pkgs affected

☕org.apache.tika:tika-core☕org.apache.tika:tika-parsers☕org.apache.tika:tika-parser-pdf-module

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

This CVE covers the same vulnerability as in CVE-2025-54988. However, this CVE expands the scope of affected packages in two ways.

First, while the entrypoint for the vulnerability was the tika-parser-pdf-module as reported in CVE-2025-54988, the vulnerability and its fix were in tika-core. Users who upgraded the tika-parser-pdf-module but did not upgrade tika-core to >= 3.2.2 would still be vulnerable.

Second, the original report failed to mention that in the 1.x Tika releases, the PDFParser was in the "org.apache.tika:tika-parsers" module.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tika:tika-core`	≥ 1.13&&< 3.2.2	3.2.2`org.apache.tika:tika-core:3.2.2`
☕Maven	`org.apache.tika:tika-parsers`	≥ 1.13&&< 2.0.0	2.0.0`org.apache.tika:tika-parsers:2.0.0`
☕Maven	`org.apache.tika:tika-parser-pdf-module`	≥ 2.0.0&&< 3.2.2	3.2.2`org.apache.tika:tika-parser-pdf-module:3.2.2`

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

chasingimpact/CVE-2025-66516-Writeup-POC

CVE-2025-66516 working exploit, scanner, explanation.

⭐ 11🍴 2Aug 2026

sid6224/CVE-2025-66516-POC

A POC for the CVE-2025-66516 Apache Tika Vulnerability for educational p

⭐ 6🍴 1Jun 2026

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tika:tika-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tika:tika-core to 3.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f58c-gq56-vjjf is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f58c-gq56-vjjf can be triaged on real exposure rather than presence alone.

Tailored to GHSA-f58c-gq56-vjjf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

How to detect GHSA-f58c-gq56-vjjf

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-f58c-gq56-vjjf -u https://target

Template: Apache Tika - XML External Entity Injection
Severity: high
Impact: Attackers can exploit XXE to read local files or cause denial of service, potentially exposing sensitive information or disrupting service.
Remediation: Upgrade tika-core to \u003E= 3.2.2 and ensure tika-pdf-module and tika-parsers are updated to latest versions.

Template by ProjectDiscovery nuclei-templates (MathematicianGoat), MIT licensed. View the full template. Scan only systems you are authorised to test.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatCritical

This vulnerability is rated Critical because it can be triggered when Apache Tika processes a maliciously crafted XFA file embedded within a PDF. Successful exploitation enables XML External Entity (XXE) injection, allowing an attacker to access sensitive local files and initiate arbitrary requests to internal or…

Product	Fixed in	Advisory
Red Hat build of Apache Camel 4.14.2 for Spring Boot 3.5.8	`tika-core`	RHSA-2025:23143
Red Hat OpenShift Dev Spaces (RHOSDS) 3.25	`devspaces/openvsx-rhel9:3.25.0-1765276570`	RHSA-2025:23225

Frequently Asked Questions

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 on all platforms allows an attacker to carry out XML External Entity injection via a crafted XFA file inside of a PDF. This CVE covers the same vulnerability as in CVE-2025-54988. However, this CVE expands the scope of affected packages in two ways. First, while the entrypoint for the vulnerability was the tika-parser-pdf-module as reported in CVE-2025-54988, the vulnerability and its fix were in tika-core. Users who upgraded the tika-parser-pdf-module but did not upgrad

O3 Security · Impact-Aware SCA

Is GHSA-f58c-gq56-vjjf in your dependencies?

O3 Security finds GHSA-f58c-gq56-vjjf across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works