Next.js: Unauthenticated Remote Code Execution in Image Optimization API when SVG files are used
Published 22 Oct 2026 · Updated 22 Oct 2026
Affected packages
- Affected
- >=10.0.0 <15.5.28
- Fixed in
- 15.5.28
npm install next@15.5.28- Affected
- >=16.0.0 <16.4.1
- Fixed in
- 16.4.1
npm install next@16.4.1Details
Impact
A memory-related vulnerability has been discovered in an upstream library used for Image Optimization can lead to possible remote code execution (RCE) when Next.js runs on glibc-based Linux.
Workaround
Ensure the version of sharp used by Next.js is greater than or equal to 0.35.5. Fresh installs automatically get a fixed version of sharp.
Upgrading Next.js to the patched versions will ensure package managers automatically provide a fixed version of sharp to Next.js.
Is GHSA-2464-fhr4-w9xw 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-2464-fhr4-w9xw
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-96889
- Linkgithub.com/vercel/next.js/commit/5e3b687b5edb868b064bdc058d768a7021e7f6ad
- Linkgithub.com/vercel/next.js/commit/9571ec899f063df6533351bec390ccb2cc0af6a3
- Packagegithub.com/vercel/next.js
- Linkgithub.com/vercel/next.js/releases/tag/v15.5.28
- Linkgithub.com/vercel/next.js/releases/tag/v16.4.1
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.