Vulnerability · Published Jul 27, 2026 · Assigned by GitHub_M

CVE-2026-64645Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname

High 8.3

In plain English

A high-severity server-side request forgery in next.js from vercel. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 36% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 4.0)8.3High
Exploit odds (30 days)0.4%top 64.1% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

Next.js is a React framework for building full-stack web applications. In versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10, a rewrites() or redirects() rule that builds its external destination hostname from request-controlled input can be pointed at an arbitrary hostname, regardless of the rule's hostname suffix. For a rewrite, Next.js proxies the request to that arbitrary host and serves the response from the application's origin, leading to Server-Side Request forgery. A redirects() rule configured this way is vulnerable to an Open Redirect. This issue has been fixed in versions 15.5.21 and 16.2.11.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
npmnext15.5.21GHSA-p9j2-gv94-2wf4
npmnext16.2.11GHSA-p9j2-gv94-2wf4

Affected products (as reported)

VendorProductVersions
vercel next.js >= 12.0.0 < 15.5.21>= 16.0.0, < 16.2.11

Weakness: CWE-918, CWE-601 · Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:L/SI:L/SA:N

References