Apache Tika vulnerable to uncontrolled memory consumptionGHSA-7qcq-xp2f-56f6
MEDIUMGHSA-7qcq-xp2f-56f6 is a medium-severity (CVSS 5.5) CWE-770 vulnerability in org.apache.tika:tika. A fix is available for org.apache.tika:tika — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.tika:tika☕org.apache.tika:tikaReal-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
The BPG parser in versions of Apache Tika before 1.28.2 and 2.4.0 may allocate an unreasonable amount of memory on carefully crafted files.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.tika:tika | all versions | 1.28.2org.apache.tika:tika:1.28.2 |
| ☕Maven | org.apache.tika:tika | ≥ 2.0.0&&< 2.4.0 | 2.4.0org.apache.tika:tika:2.4.0 |
Affected Products
tikaapacheprimavera unifieroracleDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tika:tika, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tika:tika to 1.28.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7qcq-xp2f-56f6 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is GHSA-7qcq-xp2f-56f6 in your dependencies?
Find it across Maven, including transitive dependencies.