CVE-2026-64645
SSRF and Open Redirect in Next.js rewrites/redirects via user-controlled host.
Is CVE-2026-64645 being exploited?
Not confirmed. CVE-2026-64645 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.84% probability of exploitation in the next 30 days.
How severe is CVE-2026-64645?
CVE-2026-64645 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-64645?
Yes. A fix has been recorded for CVE-2026-64645. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64645 affect?
CVE-2026-64645 affects Next.js 12.0.0 - 15.5.20, Next.js 16.0.0 - 16.2.10, Fixed in 15.5.21 and 16.2.11, Vercel/Next.js apps using rewrites()/redirects() building hostnames from requests. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64645?
Upgrade to Next.js 15.5.21 or 16.2.11+ and audit rewrites()/redirects for user-controlled host inputs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
SSRF: rewrites() can proxy to attacker-chosen hosts exposing internal resources; redirects() allow open redirects for phishing or redirect abuse.
Immediate action required
- affected>= 12.0.0 and < 15.5.21
- affected>= 16.0.0 and < 16.2.11
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.