What is GHSA-8J6J-4H2C-C65P?

GHSA-8J6J-4H2C-C65P is a critical-severity OS command injection vulnerability in require-node (npm), affecting versions < 1.3.4. It is fixed in 1.3.4, 2.0.4. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.

Which versions of require-node are affected by GHSA-8J6J-4H2C-C65P?

require-node (npm) versions < 1.3.4 is affected.

Is there a fix for GHSA-8J6J-4H2C-C65P?

Yes. GHSA-8J6J-4H2C-C65P is fixed in 1.3.4, 2.0.4. Upgrade to this version or later.

Is GHSA-8J6J-4H2C-C65P exploitable, and should I be worried?

Whether GHSA-8J6J-4H2C-C65P 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-8J6J-4H2C-C65P 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-8J6J-4H2C-C65P?

Upgrade: require-node to 1.3.4 or later, require-node to 2.0.4 or later.

GHSA-8J6J-4H2C-C65P in require-node

Q: Which versions of require-node are affected by GHSA-8J6J-4H2C-C65P?

require-node (npm) versions < 1.3.4 is affected.

Q: Is there a fix for GHSA-8J6J-4H2C-C65P?

Yes. GHSA-8J6J-4H2C-C65P is fixed in 1.3.4, 2.0.4. Upgrade to this version or later.

Q: Is GHSA-8J6J-4H2C-C65P exploitable, and should I be worried?

Whether GHSA-8J6J-4H2C-C65P 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-8J6J-4H2C-C65P 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-8J6J-4H2C-C65P?

Upgrade: require-node to 1.3.4 or later, require-node to 2.0.4 or later.

Summary

Arbitrary Code Execution in require-node

Versions of require-node prior to 1.3.4 for 1.x and 2.0.4 for 2.x are vulnerable to Arbitrary Code Execution. The package fails to sanitize requests to the require-node endpoint, allowing attackers to execute arbitrary code in the server through the injection of OS commands in the request body.

Impact

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

Affected versions

require-node (< 1.3.4) require-node (>= 2.0.0, < 2.0.4)

Security releases

require-node → 1.3.4 (npm) require-node → 2.0.4 (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

If you are using 1.x, upgrade to version 1.3.4 or later.
If you are using 2.x, upgrade to version 2.0.4 or later.

Frequently Asked Questions

What is GHSA-8J6J-4H2C-C65P? GHSA-8J6J-4H2C-C65P is a critical-severity OS command injection vulnerability in require-node (npm), affecting versions < 1.3.4. It is fixed in 1.3.4, 2.0.4. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
Which versions of require-node are affected by GHSA-8J6J-4H2C-C65P? require-node (npm) versions < 1.3.4 is affected.
Is there a fix for GHSA-8J6J-4H2C-C65P? Yes. GHSA-8J6J-4H2C-C65P is fixed in 1.3.4, 2.0.4. Upgrade to this version or later.
Is GHSA-8J6J-4H2C-C65P exploitable, and should I be worried? Whether GHSA-8J6J-4H2C-C65P 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-8J6J-4H2C-C65P 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-8J6J-4H2C-C65P?
- Upgrade require-node to 1.3.4 or later
- Upgrade require-node to 2.0.4 or later