Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Vercel | Next.Js | < 14.2.32 |
Related Weaknesses (CWE)
References
- https://github.com/vercel/next.js/commit/9c9aaed5bb9338ef31b0517ccf0ab4414f2093dPatch
- https://github.com/vercel/next.js/security/advisories/GHSA-4342-x723-ch2fVendor Advisory
- https://vercel.com/changelog/cve-2025-57822MitigationVendor Advisory
FAQ
What is CVE-2025-57822?
CVE-2025-57822 is a vulnerability with a CVSS score of 6.5 (MEDIUM). 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 i...
How severe is CVE-2025-57822?
CVE-2025-57822 has been rated MEDIUM with a CVSS base score of 6.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2025-57822?
Check the references section above for vendor advisories and patch information. Affected products include: Vercel Next.Js.