CVE-2025-57822— Next.js Improper Middleware Redirect Handling Leads to SSRF
Get alerts for future matching vulnerabilitiesLog in to subscribe
I. Basic Information for CVE-2025-57822
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗ Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
Next.js Improper Middleware Redirect Handling Leads to SSRF
Source: NVD (National Vulnerability Database)
Vulnerability 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.
Source: NVD (National Vulnerability Database)
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
Source: NVD (National Vulnerability Database)
Vulnerability Type
服务端请求伪造(SSRF)
Source: NVD (National Vulnerability Database)
Vulnerability Title
Next.js 代码问题漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Next.js是Vercel开源的一个 React 框架。 Next.js 14.2.32之前版本和15.4.7之前版本存在代码问题漏洞，该漏洞源于next函数使用不当，可能导致服务器端请求伪造。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
II. Public POCs for CVE-2025-57822
| # | POC Description | Source Link | Shenlong Link |
|---|---|---|---|
| 1 | In Next.js prior to versions 14.2.32 and 15.4.7, when request headerswere insecurely passed to NextResponse.next(), an attacker could exploit this behavior to perform Server-Side Request Forgery (SSRF) attacks. | https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2025/CVE-2025-57822.yaml | POC Details |
AI-Generated POCPremium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2025-57822
请登录查看更多情报信息。
Same Patch Batch · vercel · 2025-08-29 · 3 CVEs total
| CVE-2025-57752 | 6.2 MEDIUM | Next.js Affected by Cache Key Confusion for Image Optimization API Routes |
| CVE-2025-55173 | 4.3 MEDIUM | Next.js Content Injection Vulnerability for Image Optimization |
IV. Related Vulnerabilities
Same product: next.js
- CVE-2026-29057
Next.js: HTTP request smuggling in rewrites - CVE-2026-27980
Next.js: Unbounded next/image disk cache growth can exhaust - CVE-2026-27979
Next.js: Unbounded postponed resume buffering can lead to Do - CVE-2026-27978
Next.js: null origin can bypass Server Actions CSRF checks - CVE-2026-27977
Next.js: null origin can bypass dev HMR websocket CSRF check
Same vendor: vercel
- CVE-2026-29057
Next.js: HTTP request smuggling in rewrites - CVE-2026-27980
Next.js: Unbounded next/image disk cache growth can exhaust - CVE-2026-27979
Next.js: Unbounded postponed resume buffering can lead to Do - CVE-2026-27978
Next.js: null origin can bypass Server Actions CSRF checks - CVE-2026-27977
Next.js: null origin can bypass dev HMR websocket CSRF check
Same weakness: CWE-918
- CVE-2026-8193
Akaunting Invoice PDF Rendering dompdf.php server-side reque - CVE-2026-44313
LinkWarden: Server-Side Request Forgery (SSRF) in Link Creat - CVE-2026-42352
pygeoapi 0.23.x: Unauthenticated SSRF via OGC API - Processe - CVE-2026-42346
Postiz: TOCTOU DNS rebinding bypasses all SSRF URL validatio - CVE-2026-42339
New API: SSRF Filter Bypass via 0.0.0.0
V. Comments for CVE-2025-57822
No comments yet