Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Checkout DevGuard View on GitHub

GHSA-49mx-fj45-q3p6

HighCVSS 7.7 / 10

Published Feb 4, 2026·Last modified Feb 4, 2026

Affected Components(0)

No affected components available

Description

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 for configuration details and required environment variables.

Resources

Node.js documentation: Buffer.alloc() vs Buffer.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

Risk Scores

Base Score

7.7

The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The vulnerability can affect other systems as well, not just the initial system. There is a high impact on the confidentiality of the information.

Threat Intelligence

7.1

Exploitation activity has been observed. Apply available patches or mitigations urgently.

EPSS

N/A

Probability that this vulnerability will be exploited in the wild within the next 30 days.

Exploit

Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Related Vulnerabilities

CVE-2025-61917
Alias
EUVD-2025-206795
Alias

Browse More

High severity

Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.