CVE-2025-57822: Next.js Improper Middleware Redirect Handling Leads to SSRF
vercel · next.js
Affected: vercel next.js · Exploitation: check available, not yet exploited
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 85% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- vercel · next.js< 14.2.32; < 15.4.7
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Check available, not yet exploited. A public nuclei template can confirm it on a system you are authorised to test.
- CISA KEV
- Not listed
- Public check
- Next.js Middleware - Server-Side Request Forgery · nuclei template in projectdiscovery/nuclei-templates
- Weakness
- Server-Side Request Forgery
- Vendor
- vercel
- Published
- August 2025
CoverageNo articles yet
No CyberSIXT article names CVE-2025-57822 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.