medium6.9
CVE-2026-119347
Next.js: SVG rejection bypass in the image optimization
Impact
On self-hosted deployments, the Next.js image optimizer (`/_next/image`) can be made to process an attacker-supplied SVG even when SVG support is disabled with `dangerouslyAllowSVG: false` (the default). This reaches an SVG parser the application intended to keep disabled, increasing exposure to denial of service and SVG decoder vulnerabilities.
An attacker can exploit this over the network, without logging in, without any action by a user. If it succeeds: low risk of outages.
Affected packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| npm | next | >= 15.0.0, <= 15.5.28 | 15.5.29 |
Affected products · Vercel
| Product | Affected versions |
|---|---|
| Next.js | from 15.0.0, before 15.5.29 from 16.0.0, before 16.4.5 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/vercel/next.js/security/advisories/GHSA-7qx7-33qx-rqx2
- https://github.com/vercel/next.js/commit/4f133352e639589ad9872b9b55307b89b258e41b
- https://github.com/vercel/next.js/commit/e66e656e7d423a828bdca5f87e82cef7038c57a6
- https://github.com/vercel/next.js/releases/tag/v15.5.29
- https://github.com/vercel/next.js/releases/tag/v16.4.5
- https://nextjs.org/blog/november-2026-security-release
- https://github.com/advisories/GHSA-7qx7-33qx-rqx2
- https://nvd.nist.gov/vuln/detail/CVE-2026-119347