Next.js Fixes High-Severity SSRF and Middleware Authentication Bypass Flaws
Vulnerability Disclosure · 3 sources · Updated 4mo ago · First seen Jul 23, 2026

Vercel has patched three high-severity vulnerabilities in Next.js that could allow server-side request forgery (SSRF) and, in a narrower configuration, bypass middleware-based authentication. The flaws are tracked as CVE-2026-64645, CVE-2026-64649, and CVE-2026-64642, each rated CVSS 8.3, and affect multiple supported branches of the framework. According to the advisory coverage, the SSRF issues can be triggered under specific configurations, while the authentication bypass affects deployments using the App Router and Turbopack in a limited scenario.
The issues were fixed in Next.js 16.2.11 and 15.5.21, with no public proof-of-concept or confirmed in-the-wild exploitation reported at publication time. Defenders are advised to upgrade promptly, avoid user-controlled external destination hostnames, validate Host and X-Forwarded-Host headers, and enforce authorization checks in server-side page logic rather than relying solely on middleware protections.

