Next.js has Unbounded Memory Consumption via PPR Resume Endpoint
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:
-
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. -
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, an application must run 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.
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Paquete de npm | next | >= 16.0.0-beta.0, < 16.1.5, >= 15.0.0-canary.0, <= 15.0.0-canary.205, >= 15.0.1-canary.0, <= 15.0.1-canary.3, >= 15.0.2-canary.0, <= 15.0.2-canary.11, >= 15.0.3-canary.0, <= 15.0.3-canary.9, >= 15.0.4-canary.0, <= 15.0.4-canary.52, >= 15.1.1-canary.0, <= 15.1.1-canary.27, >= 15.2.0-canary.0, <= 15.2.0-canary.77, >= 15.2.1-canary.0, <= 15.2.1-canary.6, >= 15.2.2-canary.0, <= 15.2.2-canary.7, >= 15.3.0-canary.0, <= 15.3.0-canary.46, >= 15.3.1-canary.0, <= 15.3.1-canary.15, >= 15.4.0-canary.0, <= 15.4.0-canary.130, >= 15.4.2-canary.0, <= 15.4.2-canary.56, >= 15.5.1-canary.0, <= 15.5.1-canary.39, >= 15.6.0-canary.0, < 15.6.0-canary.61 | 16.1.5, 15.6.0-canary.61 |
Referencias
- Vector CVSS
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H- Debilidad (CWE)
CWE-400, CWE-409, CWE-770- Plataforma
- npm
- Paquete
next- Publicada
- 28.01.2026
- Actualizado
- 11.10.2026 10:22
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-5f7q-jpqc-wp7h - CC BY 4.0
Historial de vulnerabilidades: next
Todas las vulnerabilidades publicadas de este paquete (Paquete de npm), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
- Entradas en total
- 73
- Primera → última
- 12.2017 10.2026
- Sin corrección
- 0
- Explotada en ataques
- 0
Distribución por gravedad
- Crítica 5
- Alta 27
- Media 32
- Baja 9
Divulgaciones por año
- 2017: 1
- 2018: 2
- 2019: 0
- 2020: 3
- 2021: 3
- 2022: 3
- 2023: 1
- 2024: 6
- 2025: 14
- 2026: 40
-
Next.js has Unbounded Memory Consumption via PPR Resume Endpoint esta entrada
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.