vercel · Next.js · published 2026-11-16

CVE-2026-119347Next.js: SVG rejection bypass in the image optimization

Routine No exploitation evidence; EPSS 0.3%.

CVE-2026-119347 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 26% of all CVEs. This Next.js vulnerability: CVSS 6.9 (v4.0), attacks can be automated. Fixed upstream in Next.js 16.4.5, 15.5.29. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Next.js 16.4.5, 15.5.29.

Patch events

  1. This monthSecurity release

    Web frameworkNext.js

    Next.js security releases: 16.4.5, 15.5.29

    Upgrade to 16.4.515.5.29

    Why: Vendor security release for server software (most severe: CVE-2026-119347).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.3% (27th pct)FIRST EPSS v2026.06.15
CVSS base score6.9 (v4.0)
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
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →