Read the docs

Next.js image optimizer processes SVG despite rejection setting

Priority MEDIUM 46CWE-1287Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
—
Confidentiality · integrity · availability
None · None · Low
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

Next.js from 15.0.0 before 15.5.29 and from 16.0.0 before 16.4.5 is affected. Self-hosted deployments run the /_next/image optimizer on attacker-supplied SVG content even when dangerouslyAllowSVG is false, its default, because the input type is not validated (CWE-1287). A remote unauthenticated attacker can reach an SVG parser the application meant to keep disabled, increasing exposure to denial of service and SVG decoding flaws.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Description from the CNA

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.

Why it matters now

Fix Fixed next.js (vercel): 15.5.29, 16.4.5

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
vercelnext.js15.0.0 to before 15.5.29; 16.0.0 to before 16.4.515.5.29, 16.4.5Patch availableCNA
  • next.js Vendorvercel Affected 15.0.0 to before 15.5.29; 16.0.0 to before 16.4.5 Fixed in 15.5.29, 16.4.5 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:vercel:next.js:*:*:*:*:*:*:*:*——vercel
  • cpe:2.3:a:vercel:next.js:*:*:*:*:*:*:*:* Versions — — ·vercel

Remediation

Upgrade to Next.js 15.5.29 for the 15.x line or 16.4.5 for the 16.x line.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

  • Fix · CNA next.js (vercel) Fixed in 15.5.29, 16.4.5

Timeline

  1. 2026-11-16 Threatist record created from CVE-2026-119347

References

  • TI-2025-34861 Unsafe deserialization in React Server Components enables RCE KEVCVSS 3.1CRITICAL 10.0
  • TI-2025-21309 Authorization Bypass in Next.js Middleware CVSS 3.1CRITICAL 9.1
  • TI-2024-15745 An issue in Hyper on macOS version 3.4.1 and before, allows remote attackers to execute… CVSS 3.1CRITICAL 9.8
  • TI-2025-34863 Deserialization of untrusted data in Meta react-server-dom-webpack CVSS 3.1HIGH 7.5
  • TI-2024-31371 Cache Poisoning in next.js CVSS 3.1HIGH 7.5
  • TI-2023-24914 Next.js before 13.4.20-canary.13 lacks a cache-control header and thus empty prefetch… CVSS 3.1HIGH 7.5
See all 90 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences