n8n's Unsafe Buffer Allocation Allows In-Process Memory Disclosure in Task Runner
Impact
The use of Buffer.allocUnsafe() and Buffer.allocUnsafeSlow() in the task runner allowed untrusted code to allocate uninitialized memory. Such uninitialized buffers could contain residual data from within the same Node.js process (for example, data from prior requests, tasks, secrets, or tokens), resulting in potential information disclosure.
Only authenticated users are able to execute code through Task Runners.
This issue affected any deployment in which both of the following conditions were met:
- Task Runners were enabled using
N8N_RUNNERS_ENABLED=true(default: false) - Code Node was enabled (default: true)
Patches
Access to unsafe Buffer functions has been removed from the task runner sandbox. All buffer allocations are now zero-filled by default.
- Fixed in: 1.114.3 & 1.115.0
- Action: It is strongly recommended to upgrade to version ≥ 1.114.3 as soon as possible.
Changes introduced in this patch include:
- Routing all buffer allocations through
Buffer.alloc(which zero-fills) operations where applicable - Adding regression tests to ensure continued enforcement of safe allocation practices
Workarounds
If an immediate upgrade cannot be applied, the following hardening steps are recommended:
- Disable the Code Node by adding
n8n-nodes-base.codeto theNODES_EXCLUDEenvironment variable - Prefer external mode for isolation: run Task Runners in external mode so that untrusted task code executes in a separate sidecar container rather than within the main n8n process. This configuration significantly reduces the risk of in-process memory disclosure caused by unsafe buffer allocations.
In external mode, a launcher manages Task Runner processes in a dedicated sidecar environment, separate from the primary n8n instance.
See the n8n documentation for configuration details and required environment variables.
Resources
- Node.js documentation:
Buffer.alloc()vsBuffer.allocUnsafe()— background on zero-filled vs uninitialized allocations - n8n Documentation — Task Runners — external mode, setup guide, and environment configuration details
- n8n Documentation — Blocking nodes — how to globally disable specific nodes
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Paquete de npm | n8n | >= 1.65.0, < 1.114.3 | 1.114.3 |
Referencias
- Vector CVSS
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N- Debilidad (CWE)
CWE-200, CWE-668- Plataforma
- npm
- Paquete
n8n- Publicada
- 04.02.2026
- Actualizado
- 11.10.2026 10:22
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-49mx-fj45-q3p6 - CC BY 4.0
Historial de vulnerabilidades: n8n
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
- 156
- Primera → última
- 05.2023 09.2026
- Sin corrección
- 1
- Explotada en ataques
- 1
Distribución por gravedad
- Crítica 24
- Alta 58
- Media 74
Divulgaciones por año
- 2023: 3
- 2024: 0
- 2025: 14
- 2026: 139
-
n8n's Unsafe Buffer Allocation Allows In-Process Memory Disclosure in Task Runner 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.