SSRF in Vercel Next.js
CVE-2025-57822
Next.js is a React framework for building full-stack web applications. Prior to versions 14.2.32 and 15.4.7, when next() was used without explicitly passing the request object, it could lead to SSRF in self-hosted applications that incorrectly forwarded user-supplied headers. This vulnerability has been fixed in Next.js versions 14.2.32 and 15.4.7. All users implementing custom middleware logic in self-hosted environments are strongly encouraged to upgrade and verify correct usage of the next() function.
Vulnerability class: SSRF (Server-Side Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N.
EPSS exploit prediction
EPSS 0.026, 85.5th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Vercel Next.js — versions < 14.2.32, < 15.4.7
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (tanjiti/sec_profile). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- https://github.com/vercel/next.js/security/advisories/GHSA-4342-x723-ch2f (Vendor Advisory)
- https://github.com/vercel/next.js/commit/9c9aaed5bb9338ef31b0517ccf0ab4414f2093d8 (Patch)
- https://vercel.com/changelog/cve-2025-57822 (Mitigation, Vendor Advisory)