n8n's Unsafe Buffer Allocation Allows In-Process Memory Disclosure in Task Runner
CVE-2025-61917 · GHSA-49mx-fj45-q3p6 · published 2026-02-04
- Severity
- High
- CVSS score
- 7.7
- Chance of exploitation (EPSS)
- 0.40%
- Fixed in
- 1.114.3
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
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 N8NRUNNERSENABLED=true (default: false) Code Node was enabled (default: true)
Upgrade n8n to 1.114.3 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
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
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.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| n8n | npm | >= 1.65.0, < 1.114.3 | 1.114.3 |
- CriticalPhoenix: Format String Injection in applyChatTemplatearize-phoenix
- CriticalFlowise: Unauthenticated OAuth2 token refresh endpoint returns access tokens — enables token theft for any connected serviceflowise
- CriticalMLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltrationmlflow
- CriticalvLLM has RCE In Video Processingvllm
- HighConfig revision hashes could expose password verifiersopenclaw
- HighWorkspace dotenv files could override provider credentialsopenclaw
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- Criticaln8n Has an Arbitrary File Read via Git Noden8n, n8n, n8n
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- Criticaln8n has XML Node Prototype Pollution that to RCEn8n, n8n, n8n
- Criticaln8n has Prototype Pollution in XML Webhook Body Parser that Leads to RCEn8n, n8n, n8n
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.