July 2026 Security Release
Key Points
- Upgrade to v16.2.11 or v15.5.21 now
- High-severity DoS, SSRF, and middleware bypasses fixed
- Fixes available in v16.3 canary/preview
Summary
Next.js 2026-07 security release addresses multiple high- and medium-severity vulnerabilities affecting App Router, Server Actions, rewrites/redirects, Turbopack builds, and the Image Optimization API. Updates are released in v16.2.11 (Active LTS) and v15.5.21 (Maintenance LTS). Canary and preview builds also contain fixes (v16.3.0-canary.92, v16.3.0-preview.7) and the fixes will ship in v16.3.0 stable.
Upgrade commands:
npm install next@15.5.21# for 15.5 (Maintenance LTS)npm install next@16.2.11# for 16.2 (Active LTS)npm install next@16.3.0-canary.92# canarynpm install next@16.3.0-preview.7# preview
Key Points
-
Critical high-severity issues (patch immediately):
- Denial of Service in App Router using Server Actions (CVE-2026-64641) — crafted requests can cause excessive CPU and process-level request blocking.
- Middleware/proxy bypass in Turbopack-built App Router with a single locale (CVE-2026-64642) — authentication/security checks may be bypassed.
- SSRF/Open Redirect via rewrites/redirects when destination hostname is attacker-controlled (CVE-2026-64645) and SSRF from Server Actions on custom servers when Host headers are controllable (CVE-2026-64649).
-
Other medium-severity fixes to review and patch:
- DoS in Image Optimization API when optimizing remote SVGs (CVE-2026-64644).
- Unbounded Server Action payloads in the Edge runtime (CVE-2026-64646).
- Unauthenticated disclosure of internal Server Function endpoints (CVE-2026-64643).
- Cache confusion for fetch requests with bodies, including cases with invalid UTF-8 (CVE-2026-64647, CVE-2026-64648).
-
Practical guidance for engineers:
- Upgrade Next.js to one of the fixed versions above as soon as possible.
- Audit rewrites/redirects and ensure destination hostnames are not built from attacker-controlled input.
- Review Server Actions and custom server forwarding for uncontrolled Host or proxy headers.
- If self-hosting image optimization, verify remote image sources and consider disabling remote fetching until patched.
- Monitor Vercel's advisories and consider subscribing to the Open Source Bug Bounty program for coordinated disclosure.