CVE-2019-10093

In Apache Tika 1.19 to 1.21, a carefully crafted 2003ml or 2006ml file could consume all available SAXParsers in the pool and lead to very long hangs. Apache Tika users should upgrade to 1.22 or later.

Published: 2019-08-02 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-10093 is rated Moderate Risk (59.2/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 3.70%). EPSS rose +2.28% over the last day, indicating growing attacker interest. Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-10093

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 1.42% 3.70% +2.28%
2 2026-05-18 1.45% 1.42% -0.03%
3 2025-11-21 — 1.45% —

Full EPSS history (18 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-10093

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.0 MEDIUM
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2019-10093

GitHub Security Advisory for CVE-2019-10093

GHSA-4mq5-mj59-qq9c · Severity: medium · Ecosystem: maven — Allocation of Resources Without Limits or Throttling in Apache Tika

OS Trackers for CVE-2019-10093

vendor priority summary link
debian not yet assigned CVE-2019-10093 not yet assigned priority: Debian including 1 source packages (tika), 2 status rows across 2 suites (bullseye, sid): resolved 2. https://security-tracker.debian.org/tracker/CVE-2019-10093
suse medium — https://www.suse.com/security/cve/CVE-2019-10093/
ubuntu medium CVE-2019-10093 medium priority: Ubuntu including 1 source packages (tika), 6 status rows across 6 suites (bionic, disco, eoan, trusty, upstream, xenial): not-affected 2, released 2, DNE 1, ignored 1. https://ubuntu.com/security/CVE-2019-10093

Affected software / configurations for CVE-2019-10093

Vendor Product Version Raw CPE
apache tika >= 1.19, <= 1.21 cpe:2.3:a:apache:tika:*:*:*:*:*:*:*:*

References for CVE-2019-10093

cvelogic Threat Intelligence