CVE-2025-66516

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 79.8%, top 0% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Weaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 80%
CISA-KEV: Not listedEPSS: 80%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

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 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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
76(Track*)
EG Risk 76/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation80% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
99.6%
KEV
Not listed

Published

December 4, 2025

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Jun 27, 2026
No patch confirmed yet.
generic
https://lists.apache.org/thread/s5x3k93nhbkqzztp1olxotoyjpdlps9k
generic
https://cve.org/CVERecord?id=CVE-2025-54988

Vendor Advisories for CVE-2025-66516(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibtika-java (1.22-2+deb11u1build0.22.04.1) @ jammy2026-05-29ubuntu
redhatdevspaces/pluginregistry-rhel9:3.25.0-17652998282025-12-15redhat
redhattika-core2025-12-11redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 1 ecosystem)
Maven(3)
PackageVulnerable rangeFixed inDependents
org.apache.tika:tika-core1.13 ... 3.2.1 (47 versions)3.2.2—
org.apache.tika:tika-parser-pdf-module2.0.0 ... 3.2.1 (22 versions)3.2.2—
org.apache.tika:tika-parsers1.13 ... 2.0.0-BETA (25 versions)2.0.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 4× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 03:01 UTCEG score recompute▲ 1.40
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-15 16:57 UTCEPSS rescore
  6. 2026-07-15 16:57 UTCEPSS rescore
  7. 2026-07-12 05:46 UTCEPSS rescore
  8. 2026-07-08 15:15 UTCEPSS rescore
  9. 2026-07-06 08:41 UTCOSV refresh
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-04 06:30 UTCEPSS rescore
  12. 2026-07-01 15:06 UTCEPSS rescore
  13. 2026-07-01 15:06 UTCEPSS rescore
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-28 04:55 UTCEPSS rescore
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-24 10:01 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  18. 2026-06-23 21:32 UTCEPSS rescore
  19. 2026-06-23 21:32 UTCEPSS rescore
  20. 2026-06-21 14:56 UTCEPSS rescore
  21. 2026-06-21 14:56 UTCEPSS rescore
  22. 2026-06-21 01:59 UTCEPSS rescore
  23. 2026-06-21 01:59 UTCEPSS rescore
  24. 2026-06-17 20:35 UTCOSV refresh
  25. 2026-06-17 17:52 UTCEPSS rescore
Show 31 more
  1. 2026-06-15 17:48 UTCEPSS rescore
  2. 2026-06-15 17:48 UTCEPSS rescore
  3. 2026-06-14 23:18 UTCEPSS rescore
  4. 2026-06-13 23:00 UTCEPSS rescore
  5. 2026-06-13 23:00 UTCEPSS rescore
  6. 2026-06-12 23:11 UTCEPSS rescore
  7. 2026-06-11 14:00 UTCEPSS rescore
  8. 2026-06-10 22:18 UTCEPSS rescore
  9. 2026-06-10 22:18 UTCEPSS rescore
  10. 2026-06-10 13:22 UTCEPSS rescore
  11. 2026-06-08 14:17 UTCEPSS rescore
  12. 2026-06-08 14:16 UTCEPSS rescore
  13. 2026-06-07 15:24 UTCEPSS rescore
  14. 2026-06-07 15:24 UTCEPSS rescore
  15. 2026-06-05 22:46 UTCEPSS rescore
  16. 2026-06-05 22:46 UTCEPSS rescore
  17. 2026-06-05 06:10 UTCEPSS rescore
  18. 2026-06-05 06:10 UTCEPSS rescore
  19. 2026-06-04 13:12 UTCEPSS rescore
  20. 2026-06-04 13:12 UTCEPSS rescore
  21. 2026-06-02 20:13 UTCEPSS rescore
  22. 2026-06-02 20:12 UTCEPSS rescore
  23. 2026-06-01 13:51 UTCEPSS rescore
  24. 2026-06-01 13:51 UTCEPSS rescore
  25. 2026-05-31 22:30 UTCEPSS rescore
  26. 2026-05-31 22:30 UTCEPSS rescore
  27. 2026-05-31 00:16 UTCEPSS rescore
  28. 2026-05-31 00:16 UTCEPSS rescore
  29. 2026-05-29 18:24 UTCEG score recompute
  30. 2026-05-29 18:24 UTCVendor advisory
  31. 2026-05-29 13:44 UTCEPSS rescore

Publicly available exploits

(3 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCsid6224/CVE-2025-66516-POC
    First seen Dec 17, 2025

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

    Open source ↗
  • GitHub PoCchasingimpact/CVE-2025-66516-Writeup-POC
    First seen Dec 12, 2025

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

    Open source ↗
  • Nucleihttp/cves/2025/CVE-2025-66516.yaml
    First seen Jan 1, 2025

    Apache Tika - XML External Entity Injection

    Open source ↗

Frequently asked(5)

What is CVE-2025-66516?
CVE-2025-66516 is a critical vulnerability published on December 4, 2025. 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…
When was CVE-2025-66516 disclosed?
CVE-2025-66516 was first published in the National Vulnerability Database on December 4, 2025, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-66516 actively exploited?
CVE-2025-66516 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-66516?
CVE-2025-66516 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-66516?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-66516, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-66516

Explore →

Is Your Infrastructure Affected by CVE-2025-66516?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs