What is CVE-2018-15750?

CVE-2018-15750 is a medium-severity path traversal vulnerability in salt (pip), affecting versions >= 2017.7.0, < 2017.7.8. It is fixed in 2017.7.8, 2018.3.3, 2016.11.10. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.

How severe is CVE-2018-15750?

CVE-2018-15750 has a CVSS score of 5.3 (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 versions of salt are affected by CVE-2018-15750?

salt (pip) versions >= 2017.7.0, < 2017.7.8 is affected.

Is there a fix for CVE-2018-15750?

Yes. CVE-2018-15750 is fixed in 2017.7.8, 2018.3.3, 2016.11.10. Upgrade to this version or later.

Is CVE-2018-15750 exploitable, and should I be worried?

Whether CVE-2018-15750 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-2018-15750 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-2018-15750 in salt | Intelligent Application Security

Q: How severe is CVE-2018-15750?

CVE-2018-15750 has a CVSS score of 5.3 (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 versions of salt are affected by CVE-2018-15750?

salt (pip) versions >= 2017.7.0, < 2017.7.8 is affected.

Q: Is there a fix for CVE-2018-15750?

Yes. CVE-2018-15750 is fixed in 2017.7.8, 2018.3.3, 2016.11.10. Upgrade to this version or later.

Q: Is CVE-2018-15750 exploitable, and should I be worried?

Whether CVE-2018-15750 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-2018-15750 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-2018-15750?

Upgrade: salt to 2017.7.8 or later, salt to 2018.3.3 or later, salt to 2016.11.10 or later.

Summary

Directory Traversal vulnerability in salt-api in SaltStack Salt 2016.11.x before 2016.11.10, 2017.7.x before 2017.7.8 and 2018.3.x before 2018.3.3 allows remote attackers to determine which files exist on the server.

Impact

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2018-15750 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no 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 (2017.7.8, 2018.3.3, 2016.11.10); upgrading removes the vulnerable code path.

Affected versions

salt (>= 2017.7.0, < 2017.7.8) salt (>= 2018.3.0, < 2018.3.3) salt (>= 2016.11.0, < 2016.11.10)

Security releases

salt → 2017.7.8 (pip) salt → 2018.3.3 (pip) salt → 2016.11.10 (pip)

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.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

salt to 2017.7.8 or later; salt to 2018.3.3 or later; salt to 2016.11.10 or later

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

Frequently Asked Questions

What is CVE-2018-15750? CVE-2018-15750 is a medium-severity path traversal vulnerability in salt (pip), affecting versions >= 2017.7.0, < 2017.7.8. It is fixed in 2017.7.8, 2018.3.3, 2016.11.10. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
How severe is CVE-2018-15750? CVE-2018-15750 has a CVSS score of 5.3 (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 versions of salt are affected by CVE-2018-15750? salt (pip) versions >= 2017.7.0, < 2017.7.8 is affected.
Is there a fix for CVE-2018-15750? Yes. CVE-2018-15750 is fixed in 2017.7.8, 2018.3.3, 2016.11.10. Upgrade to this version or later.
Is CVE-2018-15750 exploitable, and should I be worried? Whether CVE-2018-15750 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-2018-15750 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-2018-15750?
- Upgrade salt to 2017.7.8 or later
- Upgrade salt to 2018.3.3 or later
- Upgrade salt to 2016.11.10 or later

Other vulnerabilities in salt

CVE-2025-62349 CVE-2025-62348 CVE-2024-38824 CVE-2025-22242 CVE-2025-22238