CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-64645 remediation guide

vercel next.js

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 version...

Open CVE record
Productvercel next.js
Affected versions>= >= 12.0.0 < 15.5.21, >= >= 16.0.0, < 16.2.11, >= 12.0.0 < 15.5.21, >= 16.0.0 < 16.2.11
Fixed versions15.5.21, 16.2.11
Priority basisReview · CVSS 8.3 · EPSS -
01

Identify the affected asset

Confirm whether vercel next.js is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= >= 12.0.0 < 15.5.21, >= >= 16.0.0, < 16.2.11, >= 12.0.0 < 15.5.21, >= 16.0.0 < 16.2.11. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 15.5.21, 16.2.11. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.