Description
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 value. This typically occurs on custom servers, or on deployments not behind a proxy that pins the host. Managed hosting pins the host upstream and is not affected; next start and standalone output do the same from version 14.2 onward. This issue has been fixed in versions 15.5.21 and 16.2.11.
Published: 2026-07-27
Score: 8.3 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Next.js versions 14.1.1 through 15.5.20 and 16.0.0 through 16.2.10 contain a Server‑Side Request Forgery flaw in Server Actions that allows an attacker to make the server send outbound HTTP requests to a host of the attacker’s choice by manipulating the Host header. This weakness, classified as CWE‑918, can be used to reach internal resources or external malicious hosts, potentially exposing sensitive data or enabling further exploitation.

Affected Systems

Applications built with vercel:next.js in the affected version ranges and that use Server Actions on custom servers or deployments not behind a host‑pinned proxy are impacted. Managed hosting environments that pin the host upstream are not affected, and the issue does not affect standalone or next start output from version 14.2 onward.

Risk and Exploitability

The vulnerability carries a CVSS score of 8.3, indicating high severity. The EPSS score is less than 1% and the flaw is not listed in the CISA KEV catalog. The likely attack vector is an HTTP request where the attacker controls the Host header; thus any publicly exposed endpoint that accepts Server Actions without host validation can be used. Given the high CVSS and the potential to reach internal or external systems, the risk to the affected deployments is significant.

Generated by OpenCVE AI on August 3, 2026 at 16:52 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Next.js to at least version 15.5.21 or 16.2.11, which contain the fix for the SSRF in Server Actions.
  • Ensure that any custom server or deployment configuration pins the Host header to a known trusted value for requests that trigger Server Actions, and that proxy or hosting platforms enforce host validation.
  • If upgrading immediately is not possible, add explicit validation or override of the Host header in your Server Action code to reject requests with untrusted host values, effectively blocking the SSRF vector.

Generated by OpenCVE AI on August 3, 2026 at 16:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-89xv-2m56-2m9x Next.js: Server-Side Request Forgery in Server Actions on custom servers
History

Wed, 29 Jul 2026 00:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 8.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N'}

threat_severity

Important


Tue, 28 Jul 2026 16:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 28 Jul 2026 03:30:00 +0000

Type Values Removed Values Added
First Time appeared Vercel
Vercel next.js
Vendors & Products Vercel
Vercel next.js

Mon, 27 Jul 2026 20:30:00 +0000

Type Values Removed Values Added
Description 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 value. This typically occurs on custom servers, or on deployments not behind a proxy that pins the host. Managed hosting pins the host upstream and is not affected; next start and standalone output do the same from version 14.2 onward. This issue has been fixed in versions 15.5.21 and 16.2.11.
Title Next.js: Server-Side Request Forgery in Server Actions on Custom Servers
Weaknesses CWE-918
References
Metrics cvssV4_0

{'score': 8.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-07-28T14:12:06.654Z

Reserved: 2026-07-20T17:11:30.895Z

Link: CVE-2026-64649

cve-icon Vulnrichment

Updated: 2026-07-28T14:11:58.315Z

cve-icon NVD

Status : Analyzed

Published: 2026-07-27T20:16:40.703

Modified: 2026-07-29T14:38:03.600

Link: CVE-2026-64649

cve-icon Redhat

Severity : Important

Publid Date: 2026-07-27T19:27:58Z

Links: CVE-2026-64649 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-03T17:00:06Z

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)