Skip to content
Fencer Intel
high 7.5

CVE-2018-11761 json

High severity vulnerability that affects org.apache.tika:tika-core

published 8y ago modified 4mo ago also GHSA-6jq2-789q-fff2 , EUVD-2018-0520

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
9.5%
EPSS 9.5% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

In Apache Tika 0.1 to 1.18, the XML parsers were not configured to limit entity expansion. They were therefore vulnerable to an entity expansion vulnerability which can lead to a denial of service attack.

Patch / fix

  • maven org.apache.tika:tika-core 1.19.1
  • tika Debian 11 1.20-1

debian advisories DEBIAN-CVE-2018-11761

  • hadoop Manager Server 3.2 0.18.1-3.3.3
  • lucene Manager Server 3.2 2.4.1-4.3.3
  • cobbler Manager Server 3.2 2.6.6-6.10.3
  • nekohtml Manager Server 3.2 1.9.21-3.3.3
  • spacecmd Manager Server 3.2 2.8.25.7-3.9.3
  • tika-core Manager Server 3.2 1.19.1-3.3.3
  • nutch-core Manager Server 3.2 1.0.1-7.10.3
  • susemanager Manager Server 3.2 3.2.14-3.13.3

suse advisories SUSE-RU-2018:4018-1SUSE-SU-2018:4011-1

Is CVE-2018-11761 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-11761 updated cvss 7.5

tika: XML entity expansion vulnerability due to lack of limit configuration

  • Red Hat BPM Suite 6 tika-core Red Hat JBoss BRMS 5 tika-core Red Hat JBoss BRMS 6 tika-core Red Hat JBoss Data Virtualization 6 tika-core
    affected: no fix planned “Will not fix”
  • Red Hat JBoss Fuse Integration Service 2 tika-core
    affected: no fix planned “Out of support scope”
  • Red Hat JBoss Fuse Service Works 6 tika-core Red Hat Satellite 5 tika Red Hat Software Collections rh-eclipse46-tika, rh-eclipse46-tika-java7, rh-eclipse46-tika-javadoc, rh-eclipse46-tika-parsers, rh-eclipse46-tika-serialization
    affected: no fix planned “Will not fix”
  • Red Hat Fuse 7 camel-tika camel-tika
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

9.46% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.tika:tika-core
>=0.1, <1.19.1
1.19.1

Affected products

  • Apache Software Foundation Apache Tika

Classification

Weakness
  • CWE-611 Improper Restriction of XML External Entity Reference

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.