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)
EPSS: 0.023 (81.8th percentile) — read the EPSS interpretation.
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.
Affected products
- Vercel Next.js — versions < 14.2.32, < 15.4.7
Weakness classification (CWE)
Public proof-of-concept exploits
References
- security-advisories@github.com (x_refsource_CONFIRM, Vendor Advisory)
- security-advisories@github.com (Patch, x_refsource_MISC)
- security-advisories@github.com (x_refsource_MISC, Mitigation, Vendor Advisory)
Frequently asked questions
- What is CVE-2025-57822?
- CVE-2025-57822 is a medium-severity vulnerability in Vercel Next.js, classified under Server-Side Request Forgery (SSRF). CVSS score: 6.5/10. Published 2025-08-29.
- How severe is CVE-2025-57822?
- Medium severity. CVSS v3 base score is 6.5 out of 10.
- Is CVE-2025-57822 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.