Summary
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.
Impact
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
Affected versions
Security releases
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.
Remediation advice
Upgrade to version 5.1.0.
Frequently Asked Questions
- What is GHSA-5VJ8-3V2H-H38V? GHSA-5VJ8-3V2H-H38V is a high-severity improper input validation vulnerability in next (npm), affecting versions >= 0.9.9, < 5.1.0. It is fixed in 5.1.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
- Which versions of next are affected by GHSA-5VJ8-3V2H-H38V? next (npm) versions >= 0.9.9, < 5.1.0 is affected.
- Is there a fix for GHSA-5VJ8-3V2H-H38V? Yes. GHSA-5VJ8-3V2H-H38V is fixed in 5.1.0. Upgrade to this version or later.
- Is GHSA-5VJ8-3V2H-H38V exploitable, and should I be worried? Whether GHSA-5VJ8-3V2H-H38V 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-5VJ8-3V2H-H38V 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-5VJ8-3V2H-H38V? Upgrade
nextto 5.1.0 or later.