Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

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 Aufrufe • vor 27 Tagen •via X (Twitter)

9 Kommentare

Profilbild von rixardo
rixardovor 27 Tagen

presente professor

Profilbild von 992
992vor 26 Tagen

Is there no public PoC available for this yet?

Profilbild von sy.br1d
sy.br1dvor 26 Tagen

Not yet, probably next week

Profilbild von Tomi
Tomivor 26 Tagen

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

Profilbild von sy.br1d
sy.br1dvor 26 Tagen

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

Profilbild von Tomi
Tomivor 26 Tagen

I see, thanks for the insight

Profilbild von Alex Kolovsky
Alex Kolovskyvor 27 Tagen

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

Profilbild von sy.br1d
sy.br1dvor 27 Tagen

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

Profilbild von DEGEN 👑
DEGEN 👑vor 26 Tagen

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.

Ähnliche Videos