CVE-2018-1000006

Affected versions of electron may be susceptible to a remote code execution flaw when certain conditions are met:

1. The electron application is running on Windows.
2. The electron application registers as the default handler for a protocol, such as nodeapp://.

This vulnerability is caused by a failure to sanitize additional arguments to chromium in the command line handler for Electron.

MacOS and Linux are not vulnerable.

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

CVE-2018-1000006 has a CVSS score of 8.8 (High). The vector is network-reachable, no privileges required, and user interaction required. 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.7.11, 1.6.16, 1.8.2-beta.4); upgrading removes the vulnerable code path.

Kodem intelligence

Update electron to a version that is not vulnerable. If updating is not possible, the electron team has provided the following guidance:

If for some reason you are unable to upgrade your Electron version, you can append -- as the last argument when calling app.setAsDefaultProtocolClient, which prevents Chromium from parsing further options. The double dash -- signifies the end of command options, after which only positional parameters are accepted.

app.setAsDefaultProtocolClient(protocol, process.execPath, [
  '--your-switches-here',
  '--'
])

1. What is CVE-2018-1000006? CVE-2018-1000006 is a high-severity OS command injection vulnerability in electron (npm), affecting versions >= 1.7.0, < 1.7.11. It is fixed in 1.7.11, 1.6.16, 1.8.2-beta.4. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
2. How severe is CVE-2018-1000006? CVE-2018-1000006 has a CVSS score of 8.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.
3. Which versions of electron are affected by CVE-2018-1000006? electron (npm) versions >= 1.7.0, < 1.7.11 is affected.
4. Is there a fix for CVE-2018-1000006? Yes. CVE-2018-1000006 is fixed in 1.7.11, 1.6.16, 1.8.2-beta.4. Upgrade to this version or later.
5. Is CVE-2018-1000006 exploitable, and should I be worried? Whether CVE-2018-1000006 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
6. What actually determines whether CVE-2018-1000006 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.
7. How do I fix CVE-2018-1000006?
   • Upgrade electron to 1.7.11 or later
   • Upgrade electron to 1.6.16 or later
   • Upgrade electron to 1.8.2-beta.4 or later