Unexpected server crash in Next.js.
Published 7 Dec 2021 · Updated 8 Jul 2026
Affected packages
- Affected
- >=12.0.0 <12.0.5
- Fixed in
- 12.0.5
npm install next@12.0.5- Affected
- >=0.9.9 <11.1.3
- Fixed in
- 11.1.3
npm install next@11.1.3Details
Next.js is a React framework. In versions of Next.js prior to 12.0.5 or 11.1.3, invalid or malformed URLs could lead to a server crash. In order to be affected by this issue, the deployment must use Next.js versions above 11.1.0 and below 12.0.5, Node.js above 15.0.0, and next start or a custom server. Deployments on Vercel are not affected, along with similar environments where invalid requests are filtered before reaching Next.js. Versions 12.0.5 and 11.1.3 contain patches for this issue. Note that prior version 0.9.9 package next hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.
Is GHSA-25mp-g6fv-mqxx in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected next, and gives you the command that fixes it.
References
- Linkgithub.com/vercel/next.js/security/advisories/GHSA-25mp-g6fv-mqxx
- Advisorynvd.nist.gov/vuln/detail/CVE-2021-43803
- Linkgithub.com/vercel/next.js/pull/32080
- Linkgithub.com/vercel/next.js/commit/6d98b4fb4315dec1badecf0e9bdc212a4272b264
- Packagegithub.com/vercel/next.js
- Linkgithub.com/vercel/next.js/releases/tag/v11.1.3
- Linkgithub.com/vercel/next.js/releases/v12.0.5
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.