Loading story…
A critical vulnerability, CVE-2026-94545, enables unauthenticated remote code execution in the Node.js implementation of Next.js ImageResponse/next/og when applications place attacker-controlled values into server-generated SVG elements, attributes, or styles. The issue stems from Satori failing to safely handle unescaped SVG output, allowing crafted input submitted through exposed parameters, forms, or APIs to potentially execute code on the image-generation server.
Vercel fixed the flaw in Next.js 16.3.6; versions 16.2.0 through 16.3.5 are affected. Next.js 15 and Edge-runtime ImageResponse deployments are not vulnerable, and Node.js deployments that never render untrusted data into SVG are not exposed through this condition. Organizations should identify affected installations and upgrade immediately; direct Satori users should update to 0.33.5. No public exploitation or exploit code had been reported at the time of disclosure.
See affected versions and whether adversaries are exploiting it.
4 events from the most recent confirmed update back to the earliest known activity.
Vercel fixed CVE-2026-94545 in Next.js 16.3.6. The flaw affects Next.js 16.2.0 through 16.3.5 on the Node.js runtime; Next.js 15 and Edge ImageResponse are not affected.
Affected Next.js releases became available with the release of Next.js 16.2. Versions 16.2.0 through 16.3.5 contain the vulnerable Node.js ImageResponse implementation.
Satori published an advisory for CVE-2026-94545 and released version 0.33.5 for direct users. The underlying issue involves values reaching generated SVG output without proper escaping.
Security researchers RaghavMaheshwari124 and rafabd1 reported CVE-2026-94545, a critical flaw in Node.js ImageResponse/next/og that can permit server-side code execution when attacker-controlled values are rendered into SVG content, attributes, or styles.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Next.js released **v16.3.3** and **v15.5.24** to remediate two critical unauthenticated remote-code-execution vulnerabilities. One flaw can be triggered when the Image Optimization API processes an attacker-controlled AVIF image through the `sharp` dependency and its underlying `libheif` library; Next.js disabled AVIF optimization while awaiting propagation of an upstream `libheif` fix. The second vulnerability, **CVE-2026-75604**, affects Windows-hosted applications using both the Pages Router and App Router without Cache Components; Linux and macOS deployments are not affected, and no workaround is available. The Canadian Centre for Cyber Security advised organizations running Next.js 15.5 earlier than 15.5.24 or 16.3 earlier than 16.3.3 to review the security release and apply the updates.
Sep 2, 2026
Vercel issued out-of-cycle updates for two critical unauthenticated remote-code-execution flaws in Next.js: an AVIF/HEIC image-processing heap overflow and Windows-only path traversal, tracked as `CVE-2026-75604`. The image flaw is rooted in `libheif`, reached through Next.js's `sharp` and `libvips` image-optimization chain; malicious files with duplicate alpha channels of differing bit depths can trigger a controlled heap overflow. The issue, reported with a CVSS v4 score of 9.5, was confirmed against multiple production applications, and patched Next.js releases disable AVIF optimization while an upstream dependency fix propagates. `CVE-2026-75604` affects the incremental cache on Windows because route paths do not properly escape backslashes. Attackers can use percent-encoded backslashes to leave the cache directory, read files available to the server process, and write attacker-controlled cache content to selected paths; under susceptible Server Action patterns, this can be chained to RCE. Organizations running affected Windows deployments using the Pages Router or App Router without Cache Components should upgrade to **Next.js 15.5.24 or 16.3.3**; no configuration-only mitigation is available. Linux and macOS are not affected by the cache-path flaw.
Sep 4, 2026
Vercel has patched three high-severity vulnerabilities in **Next.js** that could allow **server-side request forgery (SSRF)** and, in a narrower configuration, bypass middleware-based authentication. The flaws are tracked as `CVE-2026-64645`, `CVE-2026-64649`, and `CVE-2026-64642`, each rated **CVSS 8.3**, and affect multiple supported branches of the framework. According to the advisory coverage, the SSRF issues can be triggered under specific configurations, while the authentication bypass affects deployments using the **App Router** and **Turbopack** in a limited scenario. The issues were fixed in **Next.js 16.2.11** and **15.5.21**, with no public proof-of-concept or confirmed in-the-wild exploitation reported at publication time. Defenders are advised to upgrade promptly, avoid user-controlled external destination hostnames, validate `Host` and `X-Forwarded-Host` headers, and enforce authorization checks in server-side page logic rather than relying solely on middleware protections.
Jul 23, 2026