What is CVE-2019-10080?

CVE-2019-10080 is a medium-severity XML external entity injection (XXE) vulnerability in org.apache.nifi:nifi-security (maven), affecting versions >= 1.3.0, < 1.10.0. It is fixed in 1.10.0. An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs.

How severe is CVE-2019-10080?

CVE-2019-10080 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2019-10080?

org.apache.nifi:nifi-security (maven) versions >= 1.3.0, = 1.3.0, < 1.10.0.

Is there a fix for CVE-2019-10080?

Yes. CVE-2019-10080 is fixed in 1.10.0. Upgrade to this version or later.

Is CVE-2019-10080 exploitable, and should I be worried?

Whether CVE-2019-10080 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2019-10080 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2019-10080 in org.apache.nifi:nifi-security

Q: How severe is CVE-2019-10080?

CVE-2019-10080 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2019-10080?

org.apache.nifi:nifi-security (maven) versions >= 1.3.0, = 1.3.0, < 1.10.0.

Q: Is there a fix for CVE-2019-10080?

Yes. CVE-2019-10080 is fixed in 1.10.0. Upgrade to this version or later.

Q: Is CVE-2019-10080 exploitable, and should I be worried?

Whether CVE-2019-10080 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2019-10080 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2019-10080?

Upgrade: org.apache.nifi:nifi-security to 1.10.0 or later, org.apache.nifi:nifi to 1.10.0 or later.

Summary

Apache NiFi information disclosure by XXE

The XMLFileLookupService in NiFi versions 1.3.0 to 1.9.2 allowed trusted users to inadvertently configure a potentially malicious XML file. The XML file has the ability to make external calls to services (via XXE) and reveal information such as the versions of Java, Jersey, and Apache that the NiFI instance uses.

Impact

An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs. Typical impact: local file disclosure, server-side request forgery, or denial of service.

CVE-2019-10080 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.10.0); upgrading removes the vulnerable code path.

Affected versions

org.apache.nifi:nifi-security (>= 1.3.0, < 1.10.0) org.apache.nifi:nifi (>= 1.3.0, < 1.10.0)

Security releases

org.apache.nifi:nifi-security → 1.10.0 (maven) org.apache.nifi:nifi → 1.10.0 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.apache.nifi:nifi-security to 1.10.0 or later; org.apache.nifi:nifi to 1.10.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2019-10080? CVE-2019-10080 is a medium-severity XML external entity injection (XXE) vulnerability in org.apache.nifi:nifi-security (maven), affecting versions >= 1.3.0, < 1.10.0. It is fixed in 1.10.0. An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs.
How severe is CVE-2019-10080? CVE-2019-10080 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2019-10080?
- org.apache.nifi:nifi-security (maven) (versions >= 1.3.0, < 1.10.0)
- org.apache.nifi:nifi (maven) (versions >= 1.3.0, < 1.10.0)
Is there a fix for CVE-2019-10080? Yes. CVE-2019-10080 is fixed in 1.10.0. Upgrade to this version or later.
Is CVE-2019-10080 exploitable, and should I be worried? Whether CVE-2019-10080 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2019-10080 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2019-10080?
- Upgrade org.apache.nifi:nifi-security to 1.10.0 or later
- Upgrade org.apache.nifi:nifi to 1.10.0 or later