What is CVE-2016-15026?

CVE-2016-15026 is a high-severity XML external entity injection (XXE) vulnerability in com.googlecode.plist:dd-plist (maven), affecting versions < 1.18. It is fixed in 1.18. An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs.

How severe is CVE-2016-15026?

CVE-2016-15026 has a CVSS score of 7.8 (High). 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 versions of com.googlecode.plist:dd-plist are affected by CVE-2016-15026?

com.googlecode.plist:dd-plist (maven) versions < 1.18 is affected.

Is there a fix for CVE-2016-15026?

Yes. CVE-2016-15026 is fixed in 1.18. Upgrade to this version or later.

Is CVE-2016-15026 exploitable, and should I be worried?

Whether CVE-2016-15026 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-2016-15026 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-2016-15026 in com.googlecode.plist:dd-plist

Q: How severe is CVE-2016-15026?

CVE-2016-15026 has a CVSS score of 7.8 (High). 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 versions of com.googlecode.plist:dd-plist are affected by CVE-2016-15026?

com.googlecode.plist:dd-plist (maven) versions < 1.18 is affected.

Q: Is there a fix for CVE-2016-15026?

Yes. CVE-2016-15026 is fixed in 1.18. Upgrade to this version or later.

Q: Is CVE-2016-15026 exploitable, and should I be worried?

Whether CVE-2016-15026 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-2016-15026 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-2016-15026?

Upgrade com.googlecode.plist:dd-plist to 1.18 or later.

Summary

dd-plist XML External Entitly vulnerability

A vulnerability was found in 3breadt dd-plist 1.17 and classified as problematic. Affected by this issue is some unknown functionality. The manipulation leads to xml external entity reference. An attack has to be approached locally. Upgrading to version 1.18 is able to address this issue. The name of the patch is 8c954e8d9f6f6863729e50105a8abf3f87fff74c. It is recommended to upgrade the affected component. VDB-221486 is the identifier assigned to this vulnerability.

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-2016-15026 has a CVSS score of 7.8 (High). The vector is requires local access, 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.18); upgrading removes the vulnerable code path.

Affected versions

com.googlecode.plist:dd-plist (< 1.18)

Security releases

com.googlecode.plist:dd-plist → 1.18 (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 com.googlecode.plist:dd-plist to 1.18 or later to resolve this vulnerability.

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

Frequently Asked Questions

What is CVE-2016-15026? CVE-2016-15026 is a high-severity XML external entity injection (XXE) vulnerability in com.googlecode.plist:dd-plist (maven), affecting versions < 1.18. It is fixed in 1.18. An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs.
How severe is CVE-2016-15026? CVE-2016-15026 has a CVSS score of 7.8 (High). 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 versions of com.googlecode.plist:dd-plist are affected by CVE-2016-15026? com.googlecode.plist:dd-plist (maven) versions < 1.18 is affected.
Is there a fix for CVE-2016-15026? Yes. CVE-2016-15026 is fixed in 1.18. Upgrade to this version or later.
Is CVE-2016-15026 exploitable, and should I be worried? Whether CVE-2016-15026 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-2016-15026 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-2016-15026? Upgrade com.googlecode.plist:dd-plist to 1.18 or later.