CVE intelligence and bounded remediation
CVE-2025-57822 — Next.js is a React framework for building full-stack web applications
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.
- Severity
- High
- CVSS
- 8.2 (3.1)
- Published
- 2025-08-29
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-918
Affected products
- vercel / next.js
Matched remediation archetype
Server-side request forgery and unintended proxying
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Inventory server-side URL fetchers, webhooks, importers, previews, redirects, proxies, and protocol handlers reachable from untrusted input.
- Map egress paths to internal services, metadata endpoints, loopback, private address space, and privileged control planes.
- Review DNS resolution, redirect, proxy, credential-forwarding, and URL parsing behavior without requesting sensitive targets.
Remediate safely
- Replace arbitrary destinations with named integrations or a strict allowlist of schemes, hosts, ports, and paths.
- Resolve and validate every destination and redirect hop, then enforce egress policy independently of application checks.
- Remove ambient credentials and sensitive headers from fetchers; apply response size, time, and content limits.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.