Cyber Resilience

CVE-2024-34351

SSRF in Vercel Next.Js 13.4.0 – 14.1.1

Published
14 May 2024
Modified
10 September 2025
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.055 92th percentile
Risk Priority 83 floored blend · peak EPSS

Summary

CVE-2024-34351 is a high-severity SSRF (CWE-918) vulnerability in Vercel Next.Js. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 8% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

Next.js, a React framework for building web applications, contains a Server-Side Request Forgery vulnerability in its Server Actions feature. The flaw is present when the framework runs in self-hosted mode, Server Actions are enabled, and an action performs a redirect to a relative path beginning with a forward slash; under these conditions an attacker who can alter the Host header can cause the application to issue requests that appear to originate from the server itself. The issue was corrected in Next.js version 14.1.1.

An unauthenticated remote attacker can exploit the weakness by crafting a request that manipulates the Host header and triggers a Server Action redirect. Successful exploitation grants the ability to reach internal or otherwise restricted network resources from the perspective of the Next.js server, resulting in high-impact information disclosure as reflected by the CVSS 7.5 rating and CWE-918 classification.

The official GitHub Security Advisory GHSA-fr5h-rqp8-mj6g and the associated pull request and commit (8f7a6ca7d21a97bc9f7a1bbe10427b5ad74b9085) confirm that upgrading to Next.js 14.1.1 fully resolves the SSRF vector; no additional configuration changes are documented as required beyond the version update. The EPSS score has remained at its peak value of 0.9275 since disclosure, indicating sustained exploitation interest.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Next.js is a React framework that can provide building blocks to create web applications. A Server-Side Request Forgery (SSRF) vulnerability was identified in Next.js Server Actions. If the `Host` header is modified, and the below conditions are also met, an…

more

attacker may be able to make requests that appear to be originating from the Next.js application server itself. The required conditions are 1) Next.js is running in a self-hosted manner; 2) the Next.js application makes use of Server Actions; and 3) the Server Action performs a redirect to a relative path which starts with a `/`. This vulnerability was fixed in Next.js `14.1.1`.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-64649Same product: Vercel Next.Js
CVE-2026-44578Same product: Vercel Next.Js
CVE-2025-57822Same product: Vercel Next.Js
CVE-2025-49826Same product: Vercel Next.Js
CVE-2026-29057Same product: Vercel Next.Js
CVE-2026-27978Same product: Vercel Next.Js
CVE-2026-64645Same product: Vercel Next.Js
CVE-2024-34350Same product: Vercel Next.Js
CVE-2024-46982Same product: Vercel Next.Js
CVE-2026-44576Same product: Vercel Next.Js

Affected Assets

vercel
next.js
13.4.0 — 14.1.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.3.6
  • V1.5.3
  • V5.3.2
  • V10.4.7

Mitigating Controls (NIST 800-53 r5) AI

Information flow enforcement can restrict which destinations the server is allowed to contact on behalf of users.

Input validation directly stops untrusted URLs from being accepted and fetched without destination checks.

Boundary protection limits the network reach of server-initiated requests even if SSRF occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure development practices directly include input validation and destination allow-listing that prevent SSRF.

DE.CM-09 partial match
prevents

Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover and record SSRF flaws in web applications.

PR.IR-01 partial match
prevents

Network segmentation and egress controls can limit the damage from successful SSRF requests.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Operational threat data describing SSRF campaigns can be used to tighten outbound-request allow-lists and detection rules before attackers exploit them.

References