n8n has In-Process Memory Disclosure in its Task Runner

Summary

n8n is an open source workflow automation platform. Prior to versions 1.123.22, 2.9.3, and 2.10.1, an authenticated user with permission to create or modify workflows could use the JavaScript Task Runner to allocate uninitialized memory buffers. Uninitialized buffers may contain residual data from the same Node.js process — including data from prior requests, tasks, secrets, or tokens — resulting in information disclosure of sensitive in-process data. Task Runners must be enabled using `N8N_RUNNERS_ENABLED=true`. In external runner mode, the impact is limited to data within the external runner process. The issue has been fixed in n8n versions 1.123.22, 2.10.1 , and 2.9.3. Users should upgrade to this version or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only, and/or use external runner mode (`N8N_RUNNERS_MODE=external`) to isolate the runner process. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Timeline

1. Mar 25, 2026, 5:07 PM UTCCVE published
2. Mar 25, 2026, 8:08 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Mar 25, 2026, 8:09 PM UTCRecord last updated

Affected versions

• n8n-io n8n

  fixed in 1.123.22; From 2.0.0-rc.0 · fixed in 2.9.3; From 2.10.0 · fixed in 2.10.1

• n8nnpm

  fixed in 1.123.22

• n8nnpm

  From 2.10.0 · fixed in 2.10.1

• n8nnpm

  From 2.0.0-rc.0 · fixed in 2.9.3

References 3