CVE-2026-94545Patch

⚠️ CVE-2026-94545 (CVSS 9.5) ⚠️ Your Next.js OG image endpoint can hand an attacker a shell. 😱 If you use next/og on the Node runtime with sharp installed (what Next recommends for prod), one unauthenticated POST to that route runs commands on your server. Here's why: Satori builds the image as an SVG and drops your text in without escaping it, so an attacker breaks out of the tag and injects their own markup. It reaches the native image libs (sharp, libvips, librsvg, libxml2) and corrupts memory there, and since Node ships non-PIE, a hardcoded ROP chain lands execve every time. This is the default prod setup, not some weird edge case. 🚨 Not affected: edge runtime or no sharp — that path uses the wasm renderer. Patched in Next.js 16.3.6 / Satori 0.33.5. On 16.2.0–16.3.5? Update now. 🔥 PoC + setup: https://github.com/EQSTLab/CVE-2026-94545 #Nextjs #RCE #CVE #PoC #Exploit #CyberSecurity #nextog #CVE_2026_94545

🚨 CRITICAL NEXT.JS RCE DISCLOSED — ATTACKER-CONTROLLED SVG DATA CAN LEAD TO SERVER CODE EXECUTION Vercel has disclosed a critical remote-code-execution vulnerability affecting the Node.js implementation of ImageResponse in Next.js. • CVE-2026-94545 / GHSA-vcvr-r3jv-pc5j • CVSS 9.5 Critical • Affects Next.js >=16.2.0 and <16.3.6 • Exploitation is network-accessible and requires no authentication or user interaction, but requires an affected application configuration • Applications are vulnerable when attacker-controlled values reach SVG content, attributes or styles rendered through next/og ImageResponse • Successful exploitation can lead to remote code execution on the Node.js server • The Edge implementation of ImageResponse is NOT affected • Applications that never place attacker-controlled data into generated SVG content, attributes or styles are also not affected • Fixed in Next.js 16.3.6 • Vercel recommends removing untrusted SVG input from Node.js ImageResponse as a workaround where immediate upgrading is impossible • No confirmed in-the-wild exploitation has been identified at this time ⚠️ Analyst Note: The interesting attack surface is dynamic image generation. Open Graph/social-preview images often incorporate URL parameters, usernames, titles or other externally supplied content — exactly the type of data that can become attacker-controlled. Internet-facing Next.js applications using server-side ImageResponse should therefore review not only their framework version but whether untrusted values flow into SVG generation. Original Vercel / Next.js security advisory: https://github.com/vercel/next.js/security/advisories/GHSA-vcvr-r3jv-pc5j #NextJS #Vercel #CVE202694545 #RCE #WebSecurity #Vulnerability #ThreatIntel #DDW #DarkWeb

We recently found a new RCE chain affecting the Node.js ImageResponse implementation in Next.js. Vercel has published CVE-2026-94545. Next.js versions from 16.2.0 through 16.3.5 are affected. Upgrade to Next.js 16.3.6. I'll share more details soon, once the remaining upstream advisories are out! Credit also to @ragrocks77, who discovered this together with me Post: https://nextjs.org/blog/nextjs-security-update-september-22-2026

🚨 PoC RELEASED: A public PoC is now available for CVE-2026-94545, a critical Next.js RCE vulnerability in the Node.js implementation of ImageResponse (CVSS 9.5). An unauthenticated attacker can inject crafted SVG markup through attacker-controlled values, potentially leading to arbitrary code execution with the privileges of the Next.js server process. ⚠️ Affects Next.js 16.2.0–16.3.5. 🔴 Fixed in Next.js 16.3.6. Update immediately. PoC: https://github.com/EQSTLab/CVE-2026-94545 Source: https://github.com/vercel/next.js/security/advisories/GHSA-vcvr-r3jv-pc5j #CVE #CyberSecurity #InfoSec #NextJS #NodeJS

‼️ Next.js patched a critical ImageResponse flaw that can lead to server code execution. "CVE-2026-94545" affects 16.2.0 through 16.3.5 on Node.js when attacker-controlled values reach generated SVG. The fix is 16.3.6. Inside the bug: https://thehackernews.com/2026/09/critical-nextjs-imageresponse-flaw-can.html

⚠️ Critical NEXT.JS Flaw Enables RCE Attacks Via Weaponized SVG File Details: https://cybersecuritynews.com/critical-next-js-flaw-allows-remote-code-execution/ A critical Next.js vulnerability, tracked as CVE-2026-94545, affects the Node.js ImageResponse implementation in the next/og package and could allow remote code execution by exploiting malicious SVG content during image generation. The issue affects Next.js versions 16.2.0 through versions before 16.3.6. Developers are urged to upgrade to Next.js 16.3.6, which contains the security fix. The vulnerability exists in the Node.js ImageResponse implementation used to dynamically create Open Graph images, social-media preview images, and other server-generated graphics. #cybersecuritynews

Esse exploit está correto pra CVE-2026-94545, também adicionei ele ao repo http://github.com/rafabd1/VectorFreed junto com o PoC da CVE-2026-96889 que é falha raiz por trás deste RCE (que ainda afeta dezenas de produtos e curiosamente quase ninguém falou sobre mas ok) Mas vale destacar tbm que o exploit do RCE é muito dependente do layout da stack usada para executar o librsvg, não é universal e tbm ainda não temos um bypass de ASLR. Por isso o ideal é usar o exploit do UAF para validação inicial

Critical Next.js RCE Vulnerability Fixed in Version 16.3.6 https://securityonline.info/nextjs-rce-vulnerability-cve-2026-94545/?utm_source=twitter&utm_medium=social_share

CVE-2026-94545: public PoC for Next.js `next/og` `ImageResponse` RCE. Affected: 16.2.0–16.3.5 Patched: 16.3.6 CVSS: 9.5 PoC: https://github.com/EQSTLab/CVE-2026-94545 Advisory: https://github.com/vercel/next.js/security/advisories/GHSA-vcvr-r3jv-pc5j

A new repro landed in @pruvadev CVE-2026-94545: Next.js next/og ImageResponse RCE via Satori improper SVG escaping critical https://www.pruva.dev/reproductions/REPRO-2026-00357

A PoC/exploit has been discovered for vulnerability CVE-2026-94545 PT ID: PT-2026-97045 Vendor: Vercel Product: Next.js Description: A remote code execution vulnerability in the Node.js implementation of ImageResponse allows an unauthenticated attacker to inject malicious SVG markup through attacker-controlled values. Under the affected configuration, processing the crafted SVG can lead to arbitrary code execution with the privileges of the Next.js server process. References: • https://dbu.gs/vulnerability/PT-2026-97045 • https://github.com/EQSTLab/CVE-2026-94545

🚨 Public PoC for CVE-2026-94545. A critical Next.js next/og ImageResponse flaw can enable unauthenticated RCE through attacker-controlled SVG content. CVSS 9.5 | Affected: 16.2.0–16.3.5 | Fixed: 16.3.6 PoC: https://github.com/EQSTLab/CVE-2026-94545 🔎 https://exploitgrid.net

Your Open Graph image generator might be an RCE primitive. CVE-2026-94545 : Next.js Node ImageResponse (next/og). Improper SVG escaping via Satori → remote code execution when untrusted input lands in the image. Affected: Next.js >=16.2.0 <16.3.6 (Node runtime). Not the same risk on Edge ImageResponse. Patch to 16.3.6. tip: if your OG route does title = searchParams.get("title") and stamps it into SVG text/attrs/styles, you didn’t build a social card - you built an input sink on the server. Until you patch: stop feeding request-controlled strings into ImageResponse. Escape or don’t render them. Bookmark this if you ship Next apps. Then reply with one thing: do you generate OG images from user content? yes/no. Official: https://nextjs.org/blog/nextjs-security-update-september-22-2026

One request to a Next.js OG route replaces the Node process. Public RCE PoC landed 29 Sep!! CVE-2026-94545 (GHSA-vcvr-r3jv-pc5j). next/og ImageResponse on Next.js 16.2.0–16.3.5, Node runtime, sharp present. Satori writes the user string into the SVG unescaped. Official Node binary is non-PIE, so a fixed ROP chain reaches execve with no leak. Edge runtime and installs without sharp do not hit this path. Patched in 16.3.6 / Satori 0.33.5 https://github.com/vercel/next.js/security/advisories/GHSA-vcvr-r3jv-pc5j #Cybersecurity #AI #AISecurity #MCP #Claude #GPT #Infosec #Trending #AppSec #RCE #Nextjs

Which is the next repro? 🚨 CVE-2026-94545: Next.js next/og RCE — reproduced end-to-end. Unauth request → command execution. Affects next 16.2.0–16.3.5 &amp; satori &lt;0.33.5. We stress-tested the fix: 3 alternate trigger paths worked on 16.3.5 https://t.co/TWVKfzv9eX

🚨 Public PoC for CVE-2026-94545. A critical Next.js ImageResponse flaw can enable unauthenticated RCE through attacker-controlled SVG content in the Node.js runtime. CVSS 9.5 | Affected: 16.2.0–16.3.5 | Fixed: 16.3.6 🔎 https://exploitgrid.net/vulnerabilities/CVE-2026-94545

🚨 Public PoC released for CVE-2026-94545. A critical Next.js ImageResponse flaw can enable unauthenticated RCE through attacker-controlled SVG content in the Node.js runtime. CVSS 9.5 | Affected: 16.2.0–16.3.5 | Fixed: 16.3.6 PoC: https://github.com/EQSTLab/CVE-2026-94545

Next.jsのnext/og画像APIに影響するCVE-2026-94545の技術詳細と動作するPoCが公開された。認証なしの1リクエストからサーバー上でコマンドを実行でき、EQSTLabのデモではテスト用コンテナでrootシェルを起動した。実際の悪用は確認されていない。 問題はSatoriがJSXをSVGへ変換する際、ユーザー入力を適切にエスケープしないことに起因する。攻撃者は独自のマークアップを挿入でき、Node.jsランタイムでsharpが導入されている場合、libvipsやlibxml2によるSVG処理を経て、細工したXMLエンティティがパーサー内のメモリを破壊する。対象はNext.js 16.2.0～16.3.5とSatori 0.0.27以上0.33.5未満。Edgeランタイムやsharpなしの環境では、このRCE経路はコード実行に至らない。修正版はNext.js 16.3.6とSatori 0.33.5である。 https://securityonline.info/nextjs-rce-poc-cve-2026-94545/

There is a new urgent @nextjs vulnerability: https://thehackernews.com/2026/09/critical-nextjs-imageresponse-flaw-can.html CVE-2026-94545 allows remote code execution via ImageResponse. Please update Next.js to 16.3.6 asap. All starter kits have been updated.

CVE-2026-94545 is more than a generic next/og RCE. @PadhiyarRushi's PoC shows how unescaped SVG content reaches Satori, while a non-PIE Node binary enables a fixed ROP chain to reach execve. Affected: 16.2.0–16.3.5 Fixed: 16.3.6 PoC: https://github.com/PadhiyarRushi/CVE-2026-94545