vercel next.js up to 14.2.31/15.4.6 next server-side request forgery

Summaryinfo

A vulnerability classified as critical has been found in vercel next.js up to 14.2.31/15.4.6. The impacted element is the function Next. Performing a manipulation results in server-side request forgery. This vulnerability is cataloged as CVE-2025-57822. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in vercel next.js up to 14.2.31/15.4.6. It has been classified as critical. This affects the function next. The manipulation with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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 Middleware 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.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2025-57822 since 08/20/2025. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 14.2.32 or 15.4.7 eliminates this vulnerability. The upgrade is hosted for download at vercel.com. Applying the patch 9c9aaed5bb9338ef31b0517ccf0ab4414f2093d8 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• JavaScript Library

Vendor

• vercel

Name

• next.js

Version

• 14.2.0
• 14.2.1
• 14.2.2
• 14.2.3
• 14.2.4
• 14.2.5
• 14.2.6
• 14.2.7
• 14.2.8
• 14.2.9
• 14.2.10
• 14.2.11
• 14.2.12
• 14.2.13
• 14.2.14
• 14.2.15
• 14.2.16
• 14.2.17
• 14.2.18
• 14.2.19
• 14.2.20
• 14.2.21
• 14.2.22
• 14.2.23
• 14.2.24
• 14.2.25
• 14.2.26
• 14.2.27
• 14.2.28
• 14.2.29
• 14.2.30
• 14.2.31
• 15.4.0
• 15.4.1
• 15.4.2
• 15.4.3
• 15.4.4
• 15.4.5
• 15.4.6

License

• open-source

Website

• Product: https://github.com/vercel/next.js/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion