Critical Next.js ImageResponse Flaw Can Lead to Server Code Execution via Crafted SVG Input
Vercel patched critical Next.js ImageResponse flaw CVE-2026-94545 (CVSS 9.5) allowing server code execution via crafted SVG input; no attacks reported yet.
Vercel disclosed CVE-2026-94545, a critical flaw (CVSS 9.5) in Next.js 16.2.0 through 16.3.5 where attacker-controlled values passed into ImageResponse on the Node.js runtime can reach Satori's SVG output unescaped and trigger code execution via downstream libraries. The fix is Next.js 16.3.6, with Satori 0.33.5 fixing the underlying bug and Next.js 15.5.26 adding hardening; the Edge runtime and Next.js 15 are unaffected. As of September 23 no public attacks or exploit code had been reported, and npm audit did not flag affected versions. Workaround: keep attacker-controlled values out of SVG content, attributes, and styles.
- CVE-2026-94545 rated critical with CVSS 9.5 in Vercel's advisory, moderate 5.3 in Satori's
- Affects Next.js 16.2.0-16.3.5 using ImageResponse on Node.js runtime; fixed in 16.3.6
- Bug is unescaped attacker-controlled values in Satori's SVG output enabling code execution
- No public exploits or attacks reported; npm audit does not flag affected versions
Vulnerabilities mentioned
All| CVE | Vulnerability | CVSS | EPSS | Signals | Published |
|---|---|---|---|---|---|
| CVE-2026-94545 | Improper Output Escaping in Satori SVG Generator Exposes Next.js OG Image Pipelines | 5.3 | 1% | PoC ×5 |
From the original article
3 min read at thehackernews.com
A new security vulnerability in Next. js could allow attackers to run code on a server via ImageResponse, the feature that generates Open Graph and other social preview images, Vercel said. The risk applies when an app puts values an attacker controls, such as text read from the request URL, into the image.
thehackernews.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.