How severe is CVE-2017-15691?

CVE-2017-15691 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2017-15691?

CVE-2017-15691 affects the following packages: org.apache.uima:uimafit-core (Maven), org.apache.uima:uimaj-core (Maven), org.apache.uima:uimaj-core (Maven), org.apache.uima:uimaj-as-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2017-15691?

Update org.apache.uima:uimafit-core to 2.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-15691 is resolved across your whole dependency graph.

How do I detect CVE-2017-15691 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.uima:uimafit-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2017-15691 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2017-15691 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-15691 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-2017-15691?

CVE-2017-15691 has an EPSS (Exploit Prediction Scoring System) score of 8.9%, placing it in the 95th 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-2017-15691?

CVE-2017-15691 is classified as XML External Entity (XXE) (CWE-611). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2017-15691 published, and has it been updated?

CVE-2017-15691 was published on April 26, 2018 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

MEDIUM severity

CVE-2017-15691 — uimafit-core

MEDIUM

CVE-2017-15691 is a medium-severity (CVSS 6.5) XML External Entity (XXE) vulnerability in org.apache.uima:uimafit-core. A fix is available for org.apache.uima:uimafit-core — see the affected versions and patch details below.

Improper Restriction of XML External Entity Reference in Apache uimaj

Also known asGHSA-wp2f-hrg2-3r5m

Published

Apr 26, 2018

Updated

Oct 24, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

8.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% 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

4 pkgs affected

☕org.apache.uima:uimafit-core☕org.apache.uima:uimaj-core☕org.apache.uima:uimaj-core☕org.apache.uima:uimaj-as-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

In Apache uimaj prior to 2.10.2, Apache uimaj 3.0.0-xxx prior to 3.0.0-beta, Apache uima-as prior to 2.10.2, Apache uimaFIT prior to 2.4.0, Apache uimaDUCC prior to 2.2.2, this vulnerability relates to an XML external entity expansion (XXE) capability of various XML parsers. UIMA as part of its configuration and operation may read XML from various sources, which could be tainted in ways to cause inadvertent disclosure of local files or other internal content.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.uima:uimafit-core`	all versions	2.4.0`org.apache.uima:uimafit-core:2.4.0`
☕Maven	`org.apache.uima:uimaj-core`	all versions	2.10.2`org.apache.uima:uimaj-core:2.10.2`
☕Maven	`org.apache.uima:uimaj-core`	≥ 3.0.0-alpha&&< 3.0.0-beta	3.0.0-beta`org.apache.uima:uimaj-core:3.0.0-beta`
☕Maven	`org.apache.uima:uimaj-as-core`	all versions	2.10.2`org.apache.uima:uimaj-as-core:2.10.2`

Affected Products

4 products · 7 configurations

Application

uima-asapache

< 2.10.2

range

Application

uimaduccapache

< 2.2.2

range

Application

uimafitapache

< 2.4.0

range

Application

uimajapache

< 2.10.2

1 version

3.0.0

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.uima:uimafit-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.uima:uimafit-core to 2.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-15691 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This issue affects the versions of lucene (which contains an embedded copy of uima) as shipped with Red Hat Satellite 6.0 and 6.1. Red Hat Satellite 6.2 and later do not include lucene and are not vulnerable to this issue.

Product	Fixed in	Advisory
Red Hat Fuse 7.3.1	`uimaj`	RHSA-2019:1545

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-15691 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-611XML External Entity (XXE)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Apr 26, 2018

Last updated

Oct 24, 2026

Identifiers

CVE-2017-15691

GHSA-wp2f-hrg2-3r5m

References

Advisoryaccess.redhat.com · RHSA 2019:1545 Advisoryuima.apache.org · security report Advisorynvd.nist.gov · CVE 2017 15691 Weblists.apache.org · 00407c65738e625a8cc9d732923a4ab2d8299603cc7c7e5cc2da9c79@<commits.uima.apache.org>Weblists.apache.org · 00407c65738e625a8cc9d732923a4ab2d8299603cc7c7e5cc2da9c79@<commits.uima.apache.org>

Related vulnerabilities

Also affects uimaj-core

This CVE is medium severity; 1 of 1 other CVE affecting uimaj-core is rated as high or higher (top: high).

CVE-2022-32287

Same weakness: CWE-611

This CVE is medium severity; 7 of 7 other CVEs with CWE-611 are rated as high or higher (top: critical).

CVE-2026-108358CVE-2026-108357CVE-2026-61586CVE-2026-61741CVE-2026-61570CVE-2026-55848CVE-2026-54079Browse all CWE-611

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2017-15691 — uimafit-core

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2017-15691 in your dependencies?