CVE-2026-64649: Server-Side Request Forgery in Next.js Server Actions
- Vendor
- Vercel
CVE-2026-64649 is a server-side request forgery vulnerability affecting Next.js 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, attacker-controlled Host-associated headers can influence the outbound destination and cause the server to send the request to a malicious host. Applications are exposed when they use Server Actions and do not fix the incoming Host header to a trusted value, typically on custom servers or deployments without a host-pinning proxy. Some configurations also expose internal values that weaken middleware or proxy authorization. Managed hosting that pins the host upstream is unaffected; next start and standalone output also pin the host from version 14.2 onward.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
An attacker can redirect outbound Server Action requests to an attacker-controlled host. In some configurations, exploitation can also disclose internal values and weaken middleware or proxy authorization. The precise internal values exposed and the extent of resulting authorization compromise are not specified.
Mitigation
If you can’t patch tonight, do this now.
Prevent clients from controlling the Host-associated headers used by the application. Pin Host and X-Forwarded-Host to trusted deployment values at the edge or reverse proxy, or validate them against trusted values. For Next.js 14.2.0 and later, set the __NEXT_PRIVATE_ORIGIN environment variable to the deployment's real origin. Enforce authorization in server-side data access logic rather than relying exclusively on middleware.
Remediation
Patch, then assume compromise.
Upgrade affected deployments to Next.js 15.5.21 or 16.2.11, or a later fixed release. Affected 14.x deployments must migrate to a fixed 15.x or 16.x release because the older major branch will not receive a direct patch.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-64649 exploited in the wild?
- As of Oct 9, 2026, Mallory has no reports of CVE-2026-64649 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-64649?
- As of Oct 9, 2026, Mallory has found no public exploit for CVE-2026-64649.
- Is there a patch for CVE-2026-64649?
- Upgrade affected deployments to Next.js 15.5.21 or 16.2.11, or a later fixed release. Affected 14.x deployments must migrate to a fixed 15.x or 16.x release because the older major branch will not receive a direct patch.
- What products are affected by CVE-2026-64649?
- Vercel Next.Js.
- How severe is CVE-2026-64649?
- CVE-2026-64649 has a CVSS v4 score of 8.3 (High) and an EPSS score of 0.46% (40th percentile) as of Oct 9, 2026.
Recent activity
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.