How severe is CVE-2019-10088?

CVE-2019-10088 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-10088?

CVE-2019-10088 affects the following packages: org.apache.tika:tika-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-10088?

Update org.apache.tika:tika-core to 1.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10088 is resolved across your whole dependency graph.

How do I detect CVE-2019-10088 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 CVE-2019-10088 if there is no patch (or I can't update yet)?

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.

Is CVE-2019-10088 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-10088 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-10088?

CVE-2019-10088 has an EPSS (Exploit Prediction Scoring System) score of 4.8%, placing it in the 92th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-10088?

CVE-2019-10088 is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-10088 published, and has it been updated?

CVE-2019-10088 was published on August 2, 2019 and was last updated on October 24, 2026. 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

HIGH severity

CVE-2019-10088 — tika-core

HIGH

CVE-2019-10088 is a high-severity (CVSS 8.8) CWE-770 vulnerability in org.apache.tika:tika-core. A fix is available for org.apache.tika:tika-core — see the affected versions and patch details below.

Allocation of Resources Without Limits or Throttling in Apache Tika

Also known asGHSA-mfwh-gqx8-c787

Published

Aug 2, 2019

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

4.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk

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

1 pkg affected

☕org.apache.tika:tika-core

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

A carefully crafted or corrupt zip file can cause an OOM in Apache Tika's RecursiveParserWrapper in versions 1.7-1.21. Users should upgrade to 1.22 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tika:tika-core`	≥ 1.7&&< 1.22	1.22`org.apache.tika:tika-core:1.22`

Affected Products

1 product · 1 configurations

Application

tikaapache

≥ 1.7 && ≤ 1.21

range

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 1.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10088 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

A carefully crafted or corrupt zip file can cause an OOM in Apache Tika's RecursiveParserWrapper in versions 1.7-1.21. Users should upgrade to 1.22 or later.

O3 Security · Impact-Aware SCA

Is CVE-2019-10088 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works