How severe is GHSA-5vj8-3v2h-h38v?

No CVSS score has been assigned to GHSA-5vj8-3v2h-h38v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5vj8-3v2h-h38v?

GHSA-5vj8-3v2h-h38v affects the following packages: next (npm). Ecosystems affected: npm.

How do I fix GHSA-5vj8-3v2h-h38v?

Update next to 5.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5vj8-3v2h-h38v is resolved across your whole dependency graph.

How do I detect GHSA-5vj8-3v2h-h38v in my npm dependencies?

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

How do I mitigate GHSA-5vj8-3v2h-h38v 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-5vj8-3v2h-h38v actively exploited in the wild?

No public exploit code has been indexed for GHSA-5vj8-3v2h-h38v 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-5vj8-3v2h-h38v published, and has it been updated?

GHSA-5vj8-3v2h-h38v was published on September 4, 2020 and was last updated on April 28, 2022. 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

Remote Code Execution in nextGHSA-5vj8-3v2h-h38v

GHSA-5vj8-3v2h-h38v is a remote code execution vulnerability in next. A fix is available for next — see the affected versions and patch details below.

Published

Sep 4, 2020

Updated

Apr 28, 2022

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Apr 28, 2022 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg 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.

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

nextnpm

76.9Mdownloads / week

Description

Versions of next prior to 5.1.0 are vulnerable to Remote Code Execution. The /path: route fails to properly sanitize input and passes it to a require() call. This allows attackers to execute JavaScript code on the server. Note that prior version 0.9.9 package next npm package hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.

Recommendation

Upgrade to version 5.1.0.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`next`	≥ 0.9.9&&< 5.1.0	5.1.0`npm install next@5.1.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for next, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update next to 5.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5vj8-3v2h-h38v 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 `next` prior to 5.1.0 are vulnerable to Remote Code Execution. The `/path:` route fails to properly sanitize input and passes it to a `require()` call. This allows attackers to execute JavaScript code on the server. Note that prior version 0.9.9 package `next` npm package hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions. ## Recommendation Upgrade to version 5.1.0.

O3 Security · Impact-Aware SCA

Is GHSA-5vj8-3v2h-h38v in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works