Packages / next / Security

ModerateVulnerabilityGHSA-7qx7-33qx-rqx2CVE-2026-119347Published 19 Nov 2026

Next.js: SVG rejection bypass in the image optimization

Your version

Affected releases · next

  • 16.x16.0.0 – 16.4.4Fixed in 16.4.5
  • 15.x15.0.0 – 15.5.28Fixed in 15.5.29

On 16.x, the newest line:

npm install next@16.4.5
Every release on a timeline
16.x
  1. Affected

    16.0.0 – 16.4.4

    47 releases

  2. Fixed

    16.4.5 – 16.4.6

    2 releases

15.x
  1. Affected

    15.0.0 – 15.5.28

    82 releases

  2. Fixed

    15.5.29

    1 release

428 stable releases of next, oldest to newest, one row per major.

What happens

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.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.