Server-side Request Forgery (SSRF) Affecting next package, versions <14.2.32>=15.0.0 <15.4.2-canary.43>=15.4.3 <15.4.7
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-NEXT-12299318
- published31 Aug 2025
- disclosed29 Aug 2025
- creditNicolas Lamoureux
Introduced: 29 Aug 2025
NewCVE-2025-57822 (opens in a new tab)How to fix?
Upgrade next to version 14.2.32, 15.4.2-canary.43, 15.4.7 or higher.
Overview
next is a react framework.
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the resolve-routes. An attacker can access internal resources and potentially exfiltrate sensitive information by crafting requests containing user-controlled headers (e.g.,
Location) that are forwarded or interpreted without validation.
Note: This is only exploitable if custom middleware logic is implemented in a self-hosted deployment.