CVE-2026-119347

Next.js: SVG rejection bypass in the image optimization

Published Nov 16, 2026 CVSS 4.0 · 6.9 Medium EPSS n/a KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Next.js’s image optimizer incorrectly accepts SVG files even when dangerouslyAllowSVG is set to false, allowing the SVG to be parsed by the application’s SVG decoder. A crafted SVG uploaded through the /_next/image endpoint can trigger denial‑of‑service conditions or expose additional SVG‑related weaknesses. The flaw is identified as CWE-1287.

Affected Systems

Self‑hosted deployments of Vercel’s Next.js framework from version 15.0.0 up to but excluding 15.5.29, and from 16.4.0 up to but excluding 16.4.5, are affected. The vulnerability is fixed in versions 15.5.29 and 16.4.5 and later, which implement the proper SVG rejection policy when dangerouslyAllowSVG is false.

Risk and Exploitability

The CVSS score of 6.9 reflects moderate severity. EPSS is unavailable, so the likelihood of exploitation is unquantified, and the vulnerability is not listed in the CISA KEV catalog, indicating no known public exploits. The likely attack vector is remote: an external actor can upload a malicious SVG to the /_next/image endpoint of a vulnerable site, triggering the bypass and potentially causing a denial‑of‑service or further SVG‑based weaknesses.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Next.js framework to version 15.5.29 or 16.4.5 or later, which contain the fix for the SVG rejection bypass.
  • If an upgrade cannot be performed immediately, disable or remove the /_next/image optimizer endpoint for the affected environment and route all image uploads through a validated pipeline that rejects SVG content.
  • As a temporary protective measure, configure application‑level input validation or a web‑application firewall rule to block image files with an SVG MIME type or .svg file extension when the optimizer is in use.

Generated by OpenCVE AI on November 16, 2026 at 19:54 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Vercel
Vercel next.js
Vendors & Products Vercel
Vercel next.js
Type Values Removed Values Added
Description 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.
Title Next.js: SVG rejection bypass in the image optimization
Weaknesses CWE-1287
References
Metrics cvssV4_0

{'score': 6.9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-1287

    Improper Validation of Specified Type of Input

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 16, 2026, 6:25 PM
Reserved
Oct 29, 2026, 8:44 PM
Status
Awaiting Analysis
Published
Nov 16, 2026, 7:17 PM
Modified
Nov 16, 2026, 8:37 PM