Description
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.
Affected products
vercel: next.js
References3
- github.com/vercel/next.js/security/advisories/GHSA-4342-x723-ch… Vendor Advisory
- vercel.com/changelog/cve-2025-57822 MitigationVendor Advisory
- github.com/vercel/next.js/commit/9c9aaed5bb9338ef31b0517ccf0ab4… Patch
Metrics
- CVSS 3.1
-
8.2
HIGH
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N - EPSS — exploit probability
- 3% percentile: 85 · as of 8 November 2026
- CWE
- CWE-918
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.