CriticalGHSA-2xp9-vwfh-vxw4
Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used
Published 8 Sept 2026 · Updated 8 Sept 2026
Affected packages
nextnpm
- Affected
- >=10.0.0 <15.5.24
- Fixed in
- 15.5.24
Update to the fixed version for your release line, for example:
npm install next@15.5.24nextnpm
- Affected
- >=16.0.0 <16.3.3
- Fixed in
- 16.3.3
Update to the fixed version for your release line, for example:
npm install next@16.3.3Details
A vulnerability in the underlying libheif library used by sharp which Next.js uses for image optimization can lead to remote code execution when AVIF files are optimized.
Until a fix has propagated, optimization of AVIF files is disabled.
Is GHSA-2xp9-vwfh-vxw4 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/strukturag/libheif/security/advisories/GHSA-g89c-p67h-r497
- Linkgithub.com/vercel/next.js/security/advisories/GHSA-2xp9-vwfh-vxw4
- Linkgithub.com/vercel/next.js/pull/97875
- Linkgithub.com/vercel/next.js/pull/97931
- Linkgithub.com/vercel/next.js/commit/3a15b4ac6ac8e70b1a9b18ecc18e8434462899b3
- Linkgithub.com/vercel/next.js/commit/409772ec807def20132d251ad48fd8d8ad4c73c2
- Linkgithub.com/vercel/next.js/commit/7a5937a8ab20b89d0a961f75eabb11577f5d5998
- Packagegithub.com/vercel/next.js
- Linkgithub.com/vercel/next.js/releases/tag/v15.5.24
- Linkgithub.com/vercel/next.js/releases/tag/v16.3.3
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.