CVE-2026-64649: Next.js: Server-Side Request Forgery in Server Actions on custom servers
Impact 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.
Published Jul 22, 2026
Affected packages
next
- Ecosystem
- npm
- Affected
- >= 14.1.1, < 15.5.21
- Fixed in
- 15.5.21
- Check
npm ls next
next
- Ecosystem
- npm
- Affected
- >= 16.0.0, < 16.2.11
- Fixed in
- 16.2.11
- Check
npm ls next
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
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.
Workarounds
If you cannot upgrade, ensure clients do not control the host header your application receives. Pin or validate Host and X-Forwarded-Host at your edge or proxy. On version 14.2.0 and later, you can additionally set the __NEXT_PRIVATE_ORIGIN environment variable to your deployment's real origin:
__NEXT_PRIVATE_ORIGIN=https://www.example.com node server.jsCredited to oxqnd.
References
- https://github.com/vercel/next.js/security/advisories/GHSA-89xv-2m56-2m9x
- https://github.com/vercel/next.js/commit/b51206321854193208c0805ba42acc49287f942b
- https://github.com/vercel/next.js/commit/e3e5666ccead3a15162793d697af5e48b7cc0498
- https://github.com/vercel/next.js/releases/tag/v15.5.21
- https://github.com/vercel/next.js/releases/tag/v16.2.11
- https://github.com/advisories/GHSA-89xv-2m56-2m9x
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-119346
Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes
medium6.0Nov 19, 2026CVE-2026-119347
Next.js: SVG rejection bypass in the image optimization
medium6.9Nov 19, 2026CVE-2026-119348
Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses
medium6.3Nov 19, 2026CVE-2026-119349
Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments
medium6.3Nov 19, 2026CVE-2026-119350
Next.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params
medium6.3Nov 19, 2026CVE-2026-119351
Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata
medium6.3Nov 17, 2026
