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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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.

How does O3 Security protect against GHSA-8j6j-4h2c-c65p?

O3 pinpoints whether GHSA-8j6j-4h2c-c65p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

GHSA-8j6j-4h2c-c65p

GHSA-8j6j-4h2c-c65p is a remote code execution vulnerability in require-node. O3 Security confirms whether GHSA-8j6j-4h2c-c65p is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Arbitrary Code Execution in require-node

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

📦require-node📦require-node

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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	`require-node`	≥ 2.0.0&&< 2.0.4	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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
How O3 protects you
O3 pinpoints whether GHSA-8j6j-4h2c-c65p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-8j6j-4h2c-c65p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-8j6j-4h2c-c65p across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works