Vercel Next.js

A pre-authentication remote code execution vulnerability exists in React Server Components versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0 including the following packages: react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack. The vulnerable code unsafely deserializes payloads from HTTP requests to Server Function endpoints.

Authorization Bypass in Next.js Middleware

Next.js: Server-side request forgery in applications using WebSocket upgrades

Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale

Next.js: Server-Side Request Forgery in Server Actions on Custom Servers

Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname

Next.js Improper Middleware Redirect Handling Leads to SSRF

Next.js: Denial of Service in App Router using Server Actions

Next.js: Middleware / Proxy bypass through dynamic route parameter injection

A pre-authentication denial of service vulnerability exists in React Server Components versions 19.0.0, 19.0.1 19.1.0, 19.1.1, 19.1.2, 19.2.0 and 19.2.1, including the following packages: react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack. The vulnerable code unsafely deserializes payloads from HTTP requests to Server Function endpoints, which can cause an infinite loop that hangs the server process and may prevent future HTTP requests from being served.

Cache Poisoning in next.js

Unexpected server crash in Next.js

It was found that the fix addressing CVE-2025-55184 in React Server Components was incomplete and does not prevent a denial of service attack in a specific case. React Server Components versions 19.0.2, 19.1.3 and 19.2.2 are affected, allowing unsafe deserialization of payloads from HTTP requests to Server Function endpoints. This can cause an infinite loop that hangs the server process and may prevent future HTTP requests from being served.

Next.js Server-Side Request Forgery in Server Actions

Authorization bypass in Next.js

DOS Vulnerability in next.js

Improper CSP in Image Optimization API for Next.js

Next.js before 13.4.20-canary.13 lacks a cache-control header and thus empty prefetch responses may sometimes be cached by a CDN, causing a denial of service to all users requesting the same URL via that CDN.

Next.js Vulnerable to HTTP Request Smuggling

XSS in Image Optimization API for Next.js versions between 10.0.0 and 11.1.0

Next.js DoS vulnerability via cache poisoning

Next.js: Denial of Service in the Image Optimization API

Next.js: Unbounded next/image disk cache growth can exhaust storage

Next.js: Unbounded postponed resume buffering can lead to DoS

Next.js: Denial of Service via connection exhaustion in applications using Cache Components

Next.js: Middleware / Proxy bypass in Pages Router applications using i18n

Next.js: Middleware / Proxy bypass in App Router applications via segment-prefetch routes

Next.js: Middleware / Proxy bypass in App Router applications via segment-prefetch routes

Next.js image optimization has Denial of Service condition

A denial of service vulnerability exists in self-hosted Next.js applications that have `remotePatterns` configured for the Image Optimizer. The image optimization endpoint (`/_next/image`) loads external images entirely into memory without enforcing a maximum size limit, allowing an attacker to cause out-of-memory conditions by requesting optimization of arbitrarily large images. This vulnerability requires that `remotePatterns` is configured to allow image optimization from external domains and that the attacker can serve or control a large image on an allowed domain. Strongly consider upgrading to 15.5.10 or 16.1.5 to reduce risk and prevent availability issues in Next applications.

Next.js Denial of Service (DoS) condition

A denial of service vulnerability exists in Next.js versions with Partial Prerendering (PPR) enabled when running in minimal mode. The PPR resume endpoint accepts unauthenticated POST requests with the `Next-Resume: 1` header and processes attacker-controlled postponed state data. Two closely related vulnerabilities allow an attacker to crash the server process through memory exhaustion: 1. **Unbounded request body buffering**: The server buffers the entire POST request body into memory using `Buffer.concat()` without enforcing any size limit, allowing arbitrarily large payloads to exhaust available memory. 2. **Unbounded decompression (zipbomb)**: The resume data cache is decompressed using `inflateSync()` without limiting the decompressed output size. A small compressed payload can expand to hundreds of megabytes or gigabytes, causing memory exhaustion. Both attack vectors result in a fatal V8 out-of-memory error (`FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory`) causing the Node.js process to terminate. The zipbomb variant is particularly dangerous as it can bypass reverse proxy request size limits while still causing large memory allocation on the server. To be affected you must have an application running with `experimental.ppr: true` or `cacheComponents: true` configured along with the NEXT_PRIVATE_MINIMAL_MODE=1 environment variable. Strongly consider upgrading to 15.6.0-canary.61 or 16.1.5 to reduce risk and prevent availability issues in Next applications.

Open Redirect in Next.js versions below 11.1.0

Next.js: HTTP request smuggling in rewrites

Next.js: Denial of Service in the Image Optimization API using SVGs

Next.js: Unbounded Server Action payload in Edge runtime

Next.js: Unauthenticated Disclosure of Internal Server Function endpoints

Next.js: Response Body Cache Confusion with Invalid UTF-8 Request Bodies

Next.js Affected by Cache Key Confusion for Image Optimization API Routes

Open Redirect in Next.js