Next.js Improper Middleware Redirect Handling Leads to SSRF (CVE-2025-57822) | HOL Guard CVE

Medium · CVSS 6.5CVE-2025-57822GHSA-4342-X723-CH2F

Next.js Improper Middleware Redirect Handling Leads to SSRF

Answer in brief

CVE-2025-57822 records a Medium severity (CVSS 6.5) vulnerability in Next.js Improper Middleware Redirect Handling Leads to SSRF. The current sources do not mark it as known exploited. The current feed maps next (npm), next (npm). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 29, 2025Updated Sep 10, 2026Source checked Sep 10, 2026First seen by HOL Sep 10, 2026Material review Sep 10, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.5
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps next (npm), next (npm). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
nextnpm	>=0.9.9 <14.2.32	14.2.32
nextnpm	>=15.0.0-canary.0 <15.4.7	15.4.7

Recommended response

Check inventory. Check lockfiles and deployed manifests for next, next.
Review the reported fix. Update next to 14.2.32; next to 15.4.7 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 29, 2025
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Sep 10, 2026

Sources and claim methodology

Upstream source description

A vulnerability in **Next.js Middleware** has been fixed in **v14.2.32** and **v15.4.7**. The issue occurred when request headers were directly passed into `NextResponse.next()`. In self-hosted applications, this could allow Server-Side Request Forgery (SSRF) if certain sensitive headers from the incoming request were reflected back into the response. All users implementing custom middleware logic in self-hosted environments are strongly encouraged to upgrade and verify correct usage of the `next()` function. More details at [Vercel Changelog](https://vercel.com/changelog/cve-2025-57822)

Quoted source text, attributed separately from HOL analysis.