vercel/next.js · Security
Next.js Improper Middleware Redirect Handling Leads to SSRF
- GHSA ID
- GHSA-4342-x723-ch2f
- CVE ID
- CVE-2025-57822
- Severity
- medium
- Published
- Updated
- CVSS
- 6.5 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
- CVSS v3
- 6.5 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
Description
A vulnerability in Next.js Middleware has been fixed in v14.2.32 and v15.4.7. The issue occurred when request headers were directly passed into NextResponse.next(). In self-hosted applications, this could allow Server-Side Request Forgery (SSRF) if certain sensitive headers from the incoming request were reflected back into the response.
All users implementing custom middleware logic in self-hosted environments are strongly encouraged to upgrade and verify correct usage of the next() function.
More details at Vercel Changelog
CWEs
- CWE-918 · Server-Side Request Forgery (SSRF)
References
- https://github.com/vercel/next.js/security/advisories/GHSA-4342-x723-ch2f ↗
- https://github.com/vercel/next.js/commit/9c9aaed5bb9338ef31b0517ccf0ab4414f2093d8 ↗
- https://vercel.com/changelog/cve-2025-57822 ↗
- https://nvd.nist.gov/vuln/detail/CVE-2025-57822 ↗
- https://github.com/advisories/GHSA-4342-x723-ch2f ↗