How severe is GHSA-8j6j-4h2c-c65p?

No CVSS score has been assigned to GHSA-8j6j-4h2c-c65p yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8j6j-4h2c-c65p?

GHSA-8j6j-4h2c-c65p affects the following packages: require-node (npm), require-node (npm). Ecosystems affected: npm.

How do I fix GHSA-8j6j-4h2c-c65p?

Update require-node to 1.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8j6j-4h2c-c65p is resolved across your whole dependency graph.

How do I detect GHSA-8j6j-4h2c-c65p in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for require-node, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-8j6j-4h2c-c65p if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-8j6j-4h2c-c65p actively exploited in the wild?

No public exploit code has been indexed for GHSA-8j6j-4h2c-c65p yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-8j6j-4h2c-c65p published, and has it been updated?

GHSA-8j6j-4h2c-c65p was published on September 3, 2020 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Arbitrary Code Execution in require-nodeGHSA-8j6j-4h2c-c65p

GHSA-8j6j-4h2c-c65p is a remote code execution vulnerability in require-node. A fix is available for require-node — see the affected versions and patch details below.

Published

Sep 3, 2020

Updated

Aug 31, 2020

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

require-nodenpm

65downloads / week

Description

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.

Recommendation

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`require-node`	all versions	1.3.4`npm install require-node@1.3.4`
📦npm	`require-node`	≥ 2.0.0&&< 2.0.4	2.0.4`npm install require-node@2.0.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for require-node, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update require-node to 1.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8j6j-4h2c-c65p is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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. ## Recommendation - 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.

O3 Security · Impact-Aware SCA

Is GHSA-8j6j-4h2c-c65p in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works