Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

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 RagRocks, who discovered this...

17,651 görüntüleme • 27 gün önce •via X (Twitter)

9 Yorum

rixardo profil fotoğrafı
rixardo27 gün önce

presente professor

992 profil fotoğrafı
99227 gün önce

Is there no public PoC available for this yet?

sy.br1d profil fotoğrafı
sy.br1d27 gün önce

Not yet, probably next week

Tomi profil fotoğrafı
Tomi26 gün önce

Hi, great finding! Btw, is there a way to keep the app running even after RCE is achieved?

sy.br1d profil fotoğrafı
sy.br1d26 gün önce

If the app is using multiple workers/replicas probably, here since I used just a simple process it ends up crashing inevitably

Tomi profil fotoğrafı
Tomi26 gün önce

I see, thanks for the insight

Alex Kolovsky profil fotoğrafı
Alex Kolovsky27 gün önce

Nice find, the Node-only part is the interesting bit. Different rasterizer on that path or same lib with a different sandbox?

sy.br1d profil fotoğrafı
sy.br1d27 gün önce

Different rasterizers. Edge uses Resvg/WASM, while the Node path uses a different lib

DEGEN 👑 profil fotoğrafı
DEGEN 👑26 gün önce

What makes this wild is how the unescaped user input inside Satori's SVG parser gets passed straight down to underlying native bindings like resvg-js to pull off the full RCE.

Benzer Videolar