CVE-2026-64645: vercel next.js · Server-Side Request Forgery (SSRF)
Affects vercel next.jsSource CVE Database V5
Not known to be exploited · CVSS 8.3 High : upgrade to 16.2.11 or 15.5.21 soon.
Data as of 26 Oct 2026, 09:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-07-28.
- Patch
- Available – fixed in 16.2.11, 15.5.21
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade vercel next.js to 16.2.11 or 15.5.21.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vercelnext.js | Affected
| Fixed in
|
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.
References
- github.com/vercel/next.js/security/advisories/GHSA-p9j2-gv94-2wf4 (opens in a new tab)
- github.com/vercel/next.js/commit/35f501357e9b0fe7c950b0d6aa8fcf5343f707e9 (opens in a new tab)
- github.com/vercel/next.js/commit/d3033266c6dff23f7be71e19341fe3a8c6e2c599 (opens in a new tab)
- github.com/vercel/next.js/releases/tag/v15.5.21 (opens in a new tab)
- github.com/vercel/next.js/releases/tag/v16.2.11 (opens in a new tab)