What is GHSA-28XH-WPGR-7FM8?

GHSA-28XH-WPGR-7FM8 is a critical-severity command injection vulnerability in open (npm), affecting versions < 6.0.0. It is fixed in 6.0.0. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.

Which versions of open are affected by GHSA-28XH-WPGR-7FM8?

open (npm) versions < 6.0.0 is affected.

Is there a fix for GHSA-28XH-WPGR-7FM8?

Yes. GHSA-28XH-WPGR-7FM8 is fixed in 6.0.0. Upgrade to this version or later.

Is GHSA-28XH-WPGR-7FM8 exploitable, and should I be worried?

Whether GHSA-28XH-WPGR-7FM8 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 GHSA-28XH-WPGR-7FM8 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 GHSA-28XH-WPGR-7FM8?

Upgrade open to 6.0.0 or later.

GHSA-28XH-WPGR-7FM8 in open

Q: Which versions of open are affected by GHSA-28XH-WPGR-7FM8?

open (npm) versions < 6.0.0 is affected.

Q: Is there a fix for GHSA-28XH-WPGR-7FM8?

Yes. GHSA-28XH-WPGR-7FM8 is fixed in 6.0.0. Upgrade to this version or later.

Q: Is GHSA-28XH-WPGR-7FM8 exploitable, and should I be worried?

Whether GHSA-28XH-WPGR-7FM8 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 GHSA-28XH-WPGR-7FM8 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 GHSA-28XH-WPGR-7FM8?

Upgrade open to 6.0.0 or later.

Summary

Command Injection in open

Versions of open before 6.0.0 are vulnerable to command injection when unsanitized user input is passed in.

The package does come with the following warning in the readme:

The same care should be taken when calling open as if you were calling child_process.exec directly. If it is an executable it will run in a new shell.

Impact

Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command. Typical impact: arbitrary command execution in the application's environment.

Affected versions

open (< 6.0.0)

Security releases

open → 6.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

open is now the deprecated opn package. Upgrading to the latest version is likely have unwanted effects since it now has a very different API but will prevent this vulnerability.

Frequently Asked Questions

What is GHSA-28XH-WPGR-7FM8? GHSA-28XH-WPGR-7FM8 is a critical-severity command injection vulnerability in open (npm), affecting versions < 6.0.0. It is fixed in 6.0.0. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
Which versions of open are affected by GHSA-28XH-WPGR-7FM8? open (npm) versions < 6.0.0 is affected.
Is there a fix for GHSA-28XH-WPGR-7FM8? Yes. GHSA-28XH-WPGR-7FM8 is fixed in 6.0.0. Upgrade to this version or later.
Is GHSA-28XH-WPGR-7FM8 exploitable, and should I be worried? Whether GHSA-28XH-WPGR-7FM8 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 GHSA-28XH-WPGR-7FM8 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 GHSA-28XH-WPGR-7FM8? Upgrade open to 6.0.0 or later.