VulnerabilityAnalyzed

CVE-2025-57822

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.

HIGH 8.2EPSS 2.50%

Does this matter?

High impact if exploited, but EPSS currently rates exploitation as unlikely (2.50%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.

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 3.1: 8.2 HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
EPSS: 2.50% probability · 84th percentile
CISA KEV: Not listed
Weakness: CWE-918
Affected: vercel/next.js
Source: security-advisories@github.com

References

https://github.com/vercel/next.js/commit/9c9aaed5bb9338ef31b0517ccf0ab4414f2093d8Patch
https://github.com/vercel/next.js/security/advisories/GHSA-4342-x723-ch2fVendor Advisory
https://vercel.com/changelog/cve-2025-57822Mitigation, Vendor Advisory

Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.