CVE-2025-57822
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.
System detected CVE-2025-57822 with a risk of 3.65
System created a ticket for CVE-2025-57822
Everything after this entry will be synced with the external system. The ticket can be found at https://github.com/l3montree-dev/devguard/issues/1091
- S
Sebastian Kawelke fixed CVE-2025-57822
System detected CVE-2025-57822
System fixed CVE-2025-57822
System fixed CVE-2025-57822
System fixed CVE-2025-57822
System fixed CVE-2025-57822
System fixed CVE-2025-57822
System fixed CVE-2025-57822
System fixed CVE-2025-57822
System fixed CVE-2025-57822
System fixed CVE-2025-57822
System fixed CVE-2025-57822
System fixed CVE-2025-57822
System fixed CVE-2025-57822
System detected CVE-2025-57822
System updated the risk assessment from 0 to 3.65
System recalculated raw risk assessment
System updated the risk assessment from 3.65 to 3.81
System recalculated raw risk assessment
Add a comment
Affected component
next