CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-64649 remediation guide

vercel next.js

Next.js is a React framework for building full-stack web applications. In versions 14.1.1 through 15.5.20 and 16.0.0 through 16.2.10, when a Server Action forwards or redirects a request, an attacker can cause the server to send that outbound request to a malicious host (Server-Side Request Forgery). This requires the attacker's request to control Host-associated headers. In some configurations, it's also possible to obtain internal values that weaken middleware/proxy authorization. Applications that use Server Actions are affected when the incoming host header is not fixed to a trusted val...

Open CVE record
Productvercel next.js
Affected versions>= >= 14.1.1, < 15.5.21, >= >= 16.0.0 < 16.2.11, >= 14.1.1 < 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: >= >= 14.1.1, < 15.5.21, >= >= 16.0.0 < 16.2.11, >= 14.1.1 < 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.