Denial of Service condition in Next.js image optimization
Published 14 Oct 2024 · Updated 10 Sept 2026
Affected package
- Affected
- >=10.0.0 <14.2.7
- Fixed in
- 14.2.7
npm install next@14.2.7Details
Impact
The image optimization feature of Next.js contained a vulnerability which allowed for a potential Denial of Service (DoS) condition which could lead to excessive CPU consumption.
Not affected:
- The
next.config.jsfile is configured withimages.unoptimizedset totrueorimages.loaderset to a non-default value. - The Next.js application is hosted on Vercel.
Patches
This issue was fully patched in Next.js 14.2.7. We recommend that users upgrade to at least this version.
Workarounds
Ensure that the next.config.js file has either images.unoptimized, images.loader or images.loaderFile assigned.
Credits
Brandon Dahler (brandondahler), AWS Dimitrios Vlastaras
Is GHSA-g77x-44xx-532m 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
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.