Skip to main content
Mallory
HighVulnerability

CVE-2026-64645: SSRF and open redirect in Next.js dynamic destination hostnames

Published Jul 27, 2026 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.3High · v4
EPSS0.46%40th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Vercel
IdentifiersCVE-2026-64645CWE-918 · Server-Side Request Forgery (SSRF)

CVE-2026-64645 affects Next.js versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10. When a rewrites() or redirects() rule constructs an external destination hostname from request-controlled input, an attacker can direct it to an arbitrary hostname despite the configured hostname suffix. Vulnerable rewrite rules proxy requests to the attacker-selected host and serve its response from the application's origin, enabling server-side request forgery. Similarly configured redirect rules enable open redirects.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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 cause the application server to send requests to arbitrary hosts, including internal endpoints reachable by the server, and return their responses through the application's origin. Vulnerable redirect rules allow redirection to arbitrary external destinations. Specific sensitive-data exposure, state-changing effects, and availability consequences are not established.

Mitigation

If you can’t patch tonight, do this now.

Avoid constructing external rewrite or redirect destination hostnames from user-controlled input. If a dynamic subdomain is necessary, restrict the captured value to hostname-safe characters, such as lowercase letters, digits, and hyphens. A configured hostname suffix alone does not prevent exploitation.

Remediation

Patch, then assume compromise.

Upgrade affected Next.js deployments to version 15.5.21 or 16.2.11, or a later fixed release on the applicable branch. Deployments on older affected major versions, including 13.x and 14.x, must migrate to a fixed 15.x or 16.x release rather than expect direct patches.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
VercelNext.Jsapplication
FAQ

Frequently asked questions

Is CVE-2026-64645 exploited in the wild?
As of Oct 9, 2026, Mallory has no reports of CVE-2026-64645 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-64645?
As of Oct 9, 2026, Mallory has found no public exploit for CVE-2026-64645.
Is there a patch for CVE-2026-64645?
Upgrade affected Next.js deployments to version 15.5.21 or 16.2.11, or a later fixed release on the applicable branch. Deployments on older affected major versions, including 13.x and 14.x, must migrate to a fixed 15.x or 16.x release rather than expect direct patches.
What products are affected by CVE-2026-64645?
Vercel Next.Js.
How severe is CVE-2026-64645?
CVE-2026-64645 has a CVSS v4 score of 8.3 (High) and an EPSS score of 0.46% (40th percentile) as of Oct 9, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.