CVE-2026-119347: Next.js: SVG rejection bypass in the image optimization
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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 16.4.5 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 15.5.29
Event History
Frequently Asked Questions
Which deployments are affected?
Self-hosted Next.js deployments using the /_next/image optimizer are affected if they run versions from 15.0.0 through 15.5.28, or versions before 16.4.5 in the 16.x line.
Is the default configuration affected?
Yes. The bypass can process attacker-supplied SVG content even when dangerouslyAllowSVG is false, which is the default setting.
What does an attacker need to exploit this issue?
An attacker needs to supply SVG content that is processed by the /_next/image optimizer. Successful processing reaches an SVG parser that the application intended to keep disabled.
What is the impact of the SVG reaching the parser?
It increases exposure to denial-of-service conditions and vulnerabilities in SVG decoding.
How is the issue remediated?
Upgrade to Next.js 15.5.29 or 16.4.5, which contain the fix.