What is CVE-2016-10538?

CVE-2016-10538 is a low-severity path traversal vulnerability in cli (npm), affecting versions < 1.0.0. It is fixed in 1.0.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.

Which versions of cli are affected by CVE-2016-10538?

cli (npm) versions < 1.0.0 is affected.

Is there a fix for CVE-2016-10538?

Yes. CVE-2016-10538 is fixed in 1.0.0. Upgrade to this version or later.

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

Whether CVE-2016-10538 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-10538 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-10538 in cli

Q: Which versions of cli are affected by CVE-2016-10538?

cli (npm) versions < 1.0.0 is affected.

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

Yes. CVE-2016-10538 is fixed in 1.0.0. Upgrade to this version or later.

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

Whether CVE-2016-10538 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-10538 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.

Summary

Arbitrary File Write in cli

Affected versions of cli use predictable temporary file names. If an attacker can create a symbolic link at the location of one of these temporarly file names, the attacker can arbitrarily write to any file that the user which owns the cli process has permission to write to.

Proof of Concept

By creating Symbolic Links at the following locations, the target of the link can be written to.

lock_file = '/tmp/' + cli.app + '.pid',
log_file = '/tmp/' + cli.app + '.log';

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.

Affected versions

cli (< 1.0.0)

Security releases

cli → 1.0.0 (npm)

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

Update to version 1.0.0 or later.

Frequently Asked Questions

What is CVE-2016-10538? CVE-2016-10538 is a low-severity path traversal vulnerability in cli (npm), affecting versions < 1.0.0. It is fixed in 1.0.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
Which versions of cli are affected by CVE-2016-10538? cli (npm) versions < 1.0.0 is affected.
Is there a fix for CVE-2016-10538? Yes. CVE-2016-10538 is fixed in 1.0.0. Upgrade to this version or later.
Is CVE-2016-10538 exploitable, and should I be worried? Whether CVE-2016-10538 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-10538 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-10538? Upgrade cli to 1.0.0 or later.