Tia N.List

Reported by 5 outlets

Vercel fixed a critical Next.js RCE vulnerability in image generation. Update to patch this Next.js RCE vulnerability and secure your apps.

hot0.0
Why this score
Breadth
2.00 / 2.0 · 5 sources
Authority
1.00 / 2.0 · best outlet weight
Severity
4.50 / 5.0 · CVSS + content signals
Velocity
0.00 / 2.0 · updates in 48h
Pickup speed
0.60 / 0.6 · time to second source
Recency
× 0.00 temporal multiplier
Community
+ 0.00 / 1.5 · reddit signal
Score
0.0 / 10 = base × recency + community
securityonline.infonextjs.orggithub.combeyondmachines.netsocprime.com CVE-2026-94545 desk first seen 20d ago

Desk analysis

CVE-2026-94545 is a critical unauthenticated remote code execution flaw in the Node.js ImageResponse implementation inside next/og, affecting Next.js versions 16.2.0 through 16.3.5 with a CVSS score of 9.5. The root cause is improper escaping in SVG output produced by the upstream Satori library (GHSA-wx4j-mvgx-mqwp); when attacker-controlled values reach SVG content, attributes, or styles, the malformed output passes through the sharp rendering pipeline bundled inside the package and reaches additional vulnerable dependencies that allow arbitrary server-side code execution. The fix is Next.js 16.3.6 or Satori 0.33.5; the Edge runtime and setups without sharp are unaffected. Vercel published the vendor advisory on September 22, 2026, one day before the story first appeared, confirming the out-of-band release was driven by active researcher disclosure rather than observed exploitation.

A successful attack requires only a network-accessible endpoint that renders Open Graph images, social previews, or any server-side graphic using ImageResponse, and no authentication barrier is needed. The exposure is broad because ImageResponse is commonly embedded in marketing landing pages, API documentation, and e-commerce product routes that ingest URL parameters or user input for dynamic titles, making it easy for an attacker to reach the SVG injection point without prior reconnaissance. Unlike a typical XSS or SQL injection, this flaw executes directly on the application server, giving the attacker the same privileges as the Node.js process running the image generation route. As of September 23, 2026, no public proof-of-concept code had been released and no active exploitation reports existed, which actually increases the urgency: defenders have a narrow window to patch before exploitation tooling appears, and because npm audit did not flag the affected 16.3.5 version at that time, automated dependency scanners alone are insufficient protection.

Patch immediately to Next.js 16.3.6 (Active LTS) or 15.5.26 (hardening only for the 15.5 line), and verify the bundled Satori dependency is at 0.33.5 or later. If an immediate upgrade is not possible, remove all attacker-controlled input from SVG content, attributes, and styles rendered by the Node.js ImageResponse implementation; do not rely on switching to the deprecated Edge runtime as a workaround. For hunting, inspect server-side logs for requests hitting routes that import ImageResponse from next/og or that serve opengraph-image files, especially those containing unusual SVG payload patterns or abnormal response times from the sharp pipeline. Because the vulnerability depends on attacker-controlled input reaching the SVG layer, telemetry should focus on URL parameters, form data, or API fields that feed into image generation endpoints rather than generic web access logs. Monitor for post-exploitation behavior linked to the Node.js process spawning unexpected child processes or making outbound connections from the image generation worker.

Two developments would change the assessment significantly: the release of a public exploit or proof-of-concept for CVE-2026-94545, which would remove the current protection provided by the absence of public tooling, and confirmation from Vercel regarding whether applications hosted on Vercel's platform were automatically protected, since the company stated such protection for previous critical Next.js flaws but has not done so for this release. Additionally, publication of a CVE entry and inclusion in the GitHub Advisory Database and npm audit results would alter the detection landscape, as these mechanisms were still pending as of September 23.

Timeline

  1. original reporting

    Vercel fixed a critical Next.js RCE vulnerability in image generation. Update to patch this Next.js RCE vulnerability and secure your apps.

    securityonline.info · 20d ago · September 23rd, 2026

    Vercel fixed a critical Next.js RCE vulnerability in image generation. Update to patch this Next.js RCE vulnerability and secure your apps.

    via Mastodon https://securityonline.info/nextjs-rce-vulnerability-cve-2026-94545/?utm_source=mastodon&utm_medium=jetpack_social

  2. update from nextjs.org

    Next.js Security Update for a Critical Upstream Issue

    nextjs.org · 22d ago · September 22nd, 2026

    Vercel published the official Next.js security update on September 22, 2026. The advisory covers remote code execution in the Node.js ImageResponse implementation via an upstream Satori issue. Affected versions are Next.js >=16.2.0 <16.3.6. The fix releases are 16.3.6 (Active LTS) and 15.5.26 (Maintenance LTS, hardening only). The Edge ImageResponse implementation is not affected.

  3. update from github.com

    Remote Code Execution in next/og ImageResponse (GHSA-vcvr-r3jv-pc5j)

    github.com · 22d ago · September 22nd, 2026

    The GitHub security advisory for Next.js, published by KarimPwnz, rates the vulnerability as Critical with a CVSS score of 9.5. It affects the Node.js ImageResponse implementation from next/og when attacker-controlled values reach SVG content, attributes, or styles. The advisory links to the related upstream Satori advisory GHSA-wx4j-mvgx-mqwp and lists the fix as version 16.3.6.

  4. update from github.com

    Improper escaping in Satori-generated SVG (GHSA-wx4j-mvgx-mqwp)

    github.com · 22d ago · September 22nd, 2026

    The upstream Satori advisory, published the same day, describes improper escaping in SVG output that could lead to code execution when the SVG is used in certain contexts. It is rated Moderate (CVSS 5.3) by Satori because impact depends on downstream usage. Next.js bundles Satori and is affected because it passes SVG output into a pipeline that reaches additional vulnerable dependencies.

  5. update from beyondmachines.net

    Vercel Patches Critical Remote Code Execution Vulnerability in Next.js Image Generation Feature Vercel patched a critical vulnerability (CVE

    beyondmachines.net · 19d ago · September 24th, 2026

    Vercel Patches Critical Remote Code Execution Vulnerability in Next.js Image Generation Feature Vercel patched a critical vulnerability (CVE

    via Mastodon https://beyondmachines.net/event_details/vercel-patches-critical-remote-code-execution-vulnerability-in-next-js-image-generation-feature-t-b-3-t-f/gD2P6Ple2L

  6. update from socprime.com

    CVE-2026-94545: Critical Next.js ImageResponse Flaw Enables Remote Code Execution

    socprime.com · 19d ago · September 24th, 2026

    A critical vulnerability in Next.js could allow remote attackers to execute arbitrary code on vulnerable servers through the framework’s ImageResponse functionality. The vulnerability becomes exploitable when an application places attacker-controlled input into SVG content, attributes, or styles during server-side image generation. Under these conditions, specially crafted values can reach the SVG rendering pipeline in a way that may ultimately result in remote code execution on the application server. The issue is particularly relevant because ImageResponse is commonly used to dynamically generate Open Graph images, social media previews, and other server-rendered graphics based on application or user data. Applications that incorporate URL parameters, API data, form input, or other untrusted values into these images should be reviewed immediately. Security teams looking for CVE-2026-94545 detection content can leverage SOC Prime’s AI-Native Detection Intelligence Platform to identify suspicious exploitation and post-compromise behavior associated with vulnerable web applications. Security engineers can also use Uncoder AI to transform vulnerability intelligence into detection logic, generate hunting queries, convert indicators into platform-specific searches,

  7. update from github.com

    CVE-2026-94545 (CVSS 9.5) affects Next.js apps using next/og on the Node.js runtime with sharp.

    github.com · 13d ago · September 30th, 2026

    A vulnerable OG image endpoint could potentially allow an unauthenticated attacker to achieve remote code execution. Affected: Next.js 16.2.0–16.3.5 Fixed: Next.js 16.3.6 / Satori 0.33.5 Edge runtime or setups without sharp are reportedly not affected. If you’re running an affected version, update now. submitted by /u/thechougala [link] [comments]

    via reddit r/cybersecurity: CVE-2026-94545 (CVSS 9.5) affects Next.js apps using next/og on the Node.js runtime with sharp.

Covered in

digest 2026-09-23

Source on GitHub