n8n's Unsafe Buffer Allocation Allows In-Process Memory Disclosure in Task Runner
High7.7CVE-2025-61917 · Published Feb 4, 2026
### 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 ...
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| n8n npm | >= 1.65.0, < 1.114.3 | 1.114.3 |
Details and references
### 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.code` to the `NODES_EXCLUDE` environment 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](https://docs.n8n.io/hosting/configuration/task-runners/) for configuration details and required environment variables. ### Resources - Node.js documentation: [`Buffer.alloc()`](https://nodejs.org/docs/latest-v22.x/api/buffer.html#static-method-bufferallocsize-fill-encoding) vs [`Buffer.allocUnsafe()`](https://nodejs.org/docs/latest-v22.x/api/buffer.html#static-method-bufferallocunsafesize) , background on zero-filled vs uninitialized allocations - [n8n Documentation , Task Runners](https://docs.n8n.io/hosting/configuration/task-runners/) , external mode, setup guide, and environment configuration details - [n8n Documentation , Blocking nodes](https://docs.n8n.io/hosting/securing/blocking-nodes/) , how to globally disable specific nodes
More n8n advisories
All n8n| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Feb 4 | n8n's domain allowlist bypass enables credential exfiltration MediumFeb 4 | Medium | 1.121.0 |
| Feb 4 | n8n has a Python sandbox escapeCritical9.9Feb 4 | Critical9.9 | 2.4.8 |
| Feb 4 | n8n Merge Node has Arbitrary File Write leading to RCECriticalFeb 4 | Critical | 1.118.0+1 more |
| Feb 4 | n8n Vulnerable to Arbitrary File Write on Remote Systems via SSH NodeHighFeb 4 | High | 1.123.12+1 more |
| Feb 4 | n8n Has Stored Cross-site Scripting via Markdown Rendering in Workflow UIHighFeb 4 | High | 1.123.9+1 more |
| Feb 4 | n8n has OS Command Injection in Git NodeCriticalFeb 4 | Critical | 1.123.10+1 more |