Next.js is a React framework for building full-stack web applications. In versions 14.1.1 through 15.5.20 and 16.0.0 through 16.2.10, when a Server Action forwards or redirects a request, an attacker can cause the server to send that outbound request to a malicious host (Server-Side Request Forgery). This requires the attacker's request to control Host-associated headers. In some configurations, it's also possible to obtain internal values that weaken middleware/proxy authorization. Applications that use Server Actions are affected when the incoming host header is not fixed to a trusted value. This typically occurs on custom servers, or on deployments not behind a proxy that pins the host. Managed hosting pins the host upstream and is not affected; next start and standalone output do the same from version 14.2 onward. This issue has been fixed in versions 15.5.21 and 16.2.11.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XVercel Next.js
APPVercel14.1.1 – 15.5.21 (excl.)16.0.0 – 16.2.11 (excl.)
Related vulnerabilities
RCE bez uwierzytelnienia w React Server Components (deserializacja)
Pominięcie autoryzacji w middleware Next.js przez nagłówek x-middleware-subrequest
Vercel Next.js — nadmierne zużycie CPU przez spreparowane żądania (DoS)
Ominięcie uwierzytelniania middleware w Next.js App Router z Turbopack
Next.js: SSRF i Open Redirect przez niekontrolowane reguły rewrites/redirects