Next.js: SVG rejection bypass in the image optimization
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in next 15.5.29 and next 16.4.5.
Next.js is a React framework for building full-stack web applications. From 15.0.0 until 15.5.29 and 16.4.5, the /_next/image optimizer in self-hosted Next.js deployments can process attacker-supplied SVG content even when dangerouslyAllowSVG is false, which is the default. The SVG reaches a parser that the application intended to keep disabled, increasing exposure to denial of service and vulnerabilities in SVG decoding. This issue is fixed in versions 16.4.5 and 15.5.29.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| vercel | >=15.0.0 <15.5.29, >=16.0.0 <16.4.5 | ||
| npm: next | >=15.0.0 <15.5.29, >=15.0.0 <=15.5.28, >=16.0.0 <16.4.5, >=16.0.0 <=16.4.4 | 15.5.29, 16.4.5 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in next (npm), strongest first
Embed
A live severity badge for an advisory, README or ticket