In Apache Tika 0.1 to 1.18, the XML parsers were not configured to limit entity expansion.
Noroxi assessment
Priority: Monitor (action score 33/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 9.3% (FIRST EPSS); higher than 95.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: tika (Debian:11) 1.20-1; org.apache.tika:tika-core (Maven) 1.19.1; spacewalk-web (SUSE:Manager Proxy 3.2) 2.8.7.11-3.13.3.
Low priority for now. Upgrade to tika (Debian:11) 1.20-1; org.apache.tika:tika-core (Maven) 1.19.1; spacewalk-web (SUSE:Manager Proxy 3.2) 2.8.7.11-3.13.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 19, 2018
- Updated
- Jun 16, 2026
- EPSS
- 9.3% · 95th percentile
- CWE
- CWE-611
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 3 / 30 · 9.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| apache | tika | cpe:2.3:a:apache:tika |
| oracle | business process management suite | cpe:2.3:a:oracle:business_process_management_suite |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache tika0.1 and later · up to 1.18 inclusive
- oracle business process management suite12.1.3.0.0
- oracle business process management suite12.2.1.3.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.
Apache Software Foundation Apache Tika
- 0.1 to 1.18affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | tika | before 1.20-1 | 1.20-1 |
| Maven | org.apache.tika:tika-core | from 0.1 · before 1.19.1 | 1.19.1 |
| SUSE:Manager Proxy 3.2 | spacewalk-web | before 2.8.7.11-3.13.3 | 2.8.7.11-3.13.3 |
| SUSE:Manager Server 3.2 | apache-mybatis | before 3.2.3-3.3.3 | 3.2.3-3.3.3 |
| SUSE:Manager Server 3.2 | cobbler | before 2.6.6-6.10.3 | 2.6.6-6.10.3 |
| SUSE:Manager Server 3.2 | hadoop | before 0.18.1-3.3.3 | 0.18.1-3.3.3 |
| SUSE:Manager Server 3.2 | image-sync-formula | before 0.1.1542287363.b8aa274-3.6.3 | 0.1.1542287363.b8aa274-3.6.3 |
| SUSE:Manager Server 3.2 | lucene | before 2.4.1-4.3.3 | 2.4.1-4.3.3 |
| SUSE:Manager Server 3.2 | nekohtml | before 1.9.21-3.3.3 | 1.9.21-3.3.3 |
| SUSE:Manager Server 3.2 | nutch-core | before 1.0.1-7.10.3 | 1.0.1-7.10.3 |
| SUSE:Manager Server 3.2 | picocontainer | before 1.3.7-3.3.3 | 1.3.7-3.3.3 |
| SUSE:Manager Server 3.2 | python-susemanager-retail | before 1.0.1542643545.8752d17-2.6.3 | 1.0.1542643545.8752d17-2.6.3 |
| SUSE:Manager Server 3.2 | salt-netapi-client | before 0.15.0-4.3.3 | 0.15.0-4.3.3 |
| SUSE:Manager Server 3.2 | saltboot-formula | before 0.1.1542287363.b8aa274-3.6.3 | 0.1.1542287363.b8aa274-3.6.3 |
| SUSE:Manager Server 3.2 | spacecmd | before 2.8.25.7-3.9.3 | 2.8.25.7-3.9.3 |
| SUSE:Manager Server 3.2 | spacewalk-branding | before 2.8.5.12-3.10.4 | 2.8.5.12-3.10.4 |
| SUSE:Manager Server 3.2 | spacewalk-config | before 2.8.5.5-3.10.3 | 2.8.5.5-3.10.3 |
| SUSE:Manager Server 3.2 | spacewalk-java | before 2.8.78.13-3.13.1 | 2.8.78.13-3.13.1 |
| SUSE:Manager Server 3.2 | spacewalk-search | before 2.8.3.7-3.12.3 | 2.8.3.7-3.12.3 |
| SUSE:Manager Server 3.2 | spacewalk-setup | before 2.8.7.5-3.10.3 | 2.8.7.5-3.10.3 |
| SUSE:Manager Server 3.2 | spacewalk-utils | before 2.8.18.3-3.3.3 | 2.8.18.3-3.3.3 |
| SUSE:Manager Server 3.2 | susemanager | before 3.2.14-3.13.3 | 3.2.14-3.13.3 |
| SUSE:Manager Server 3.2 | susemanager-docs_en | before 3.2-11.12.3 | 3.2-11.12.3 |
| SUSE:Manager Server 3.2 | susemanager-frontend-libs | before 3.2.4-3.7.3 | 3.2.4-3.7.3 |
+4
Same product
apache: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-66516Apache Tika core, Apache Tika parsers, Apache Tika PDF parser module: Update to CVE-2025-54988 to expand scope of artifacts affected66This week
- CVE-2018-1335From Apache Tika versions 1.7 to 1.17, clients could send carefully crafted headers to tika-server that could be used to inject commands int60This week
- CVE-2025-54988Apache Tika PDF parser module: XXE vulnerability in PDFParser's handling of XFA48Plan
Published before and after this one in the same product
- ← EarlierCVE-2018-1338Apr 25, 2018 · A carefully crafted (or fuzzed) file can trigger an infinite loop in Apache Tika's BPGParser in versions of Apache Tika before 1.18.23Monitor
- ← EarlierCVE-2018-1339Apr 25, 2018 · A carefully crafted (or fuzzed) file can trigger an infinite loop in Apache Tika's ChmParser in versions of Apache Tika before 1.18.23Monitor
- Later →CVE-2018-11762Sep 19, 2018 · In Apache Tika 0.9 to 1.18, in a rare edge case where a user does not specify an extract directory on the commandline (--extract-dir=) and t25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:tika | 1.20-1 · Debian:11 | Package registry (OSV) |
| Maven:org.apache.tika:tika-core | 1.19.1 | Package registry (OSV) |
| suse:apache-mybatis | 3.2.3-3.3.3 · SUSE:Manager Server 3.2 | Package registry (OSV) |
| suse:cobbler | 2.6.6-6.10.3 · SUSE:Manager Server 3.2 | Package registry (OSV) |
| suse:hadoop | 0.18.1-3.3.3 · SUSE:Manager Server 3.2 | Package registry (OSV) |
| suse:image-sync-formula | 0.1.1542287363.b8aa274-3.6.3 · SUSE:Manager Server 3.2 | Package registry (OSV) |
| suse:lucene | 2.4.1-4.3.3 · SUSE:Manager Server 3.2 | Package registry (OSV) |
| suse:nekohtml | 1.9.21-3.3.3 · SUSE:Manager Server 3.2 | Package registry (OSV) |
| suse:nutch-core | 1.0.1-7.10.3 · SUSE:Manager Server 3.2 | Package registry (OSV) |
| suse:picocontainer | 1.3.7-3.3.3 · SUSE:Manager Server 3.2 | Package registry (OSV) |
| suse:python-susemanager-retail | 1.0.1542643545.8752d17-2.6.3 · SUSE:Manager Server 3.2 | Package registry (OSV) |
| suse:salt-netapi-client | 0.15.0-4.3.3 · SUSE:Manager Server 3.2 | Package registry (OSV) |
| suse:saltboot-formula | 0.1.1542287363.b8aa274-3.6.3 · SUSE:Manager Server 3.2 | Package registry (OSV) |
| suse:spacewalk-web | 2.8.7.11-3.13.3 · SUSE:Manager Proxy 3.2 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:9 | 2019-01-23 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+126 d
- TodayOct 20, 2026+2953 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-611 · Improper Restriction of XML External Entity ReferenceCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
- lists.apache.org/thread.html/5553e10bba5604117967466618f219c0cae710075819c70cfb3fb421%40%3Cdev.tika.apache.org%3E
- lists.apache.org/thread.html/708d94141126eac03011144a971a6411fcac16d9c248d1d535a39451%40%3Csolr-user.lucene.apache.org%3E
- www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.