CVE-2026-27496
published 2026-03-25CVE-2026-27496: 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…
PriorityP338medium6.5CVSS 3.1
AVNACLPRLUINSUCHINAN
EPSS
0.26%
17.5th percentile
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.
Affected
9 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| n8n-io | n8n | < 1.123.22 | 1.123.22 |
| n8n-io | n8n | — | — |
| n8n-io | n8n | — | — |
| n8n | n8n | < 1.123.22 | 1.123.22 |
| n8n | n8n | — | — |
| n8n | n8n | >= 0 < 1.123.22 | 1.123.22 |
| n8n | n8n | >= 2.0.0 < 2.9.3 | 2.9.3 |
| n8n | n8n | >= 2.0.0-rc.0 < 2.9.3 | 2.9.3 |
| n8n | n8n | >= 2.10.0 < 2.10.1 | 2.10.1 |
CVSS provenance
nvdv3.16.5MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvdv4.07.1HIGHCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
n8n has In-Process Memory Disclosure in its Task Runner
ghsa·2026-03-25
CVE-2026-27496 [HIGH] CWE-908 n8n has In-Process Memory Disclosure in its Task Runner
n8n has In-Process Memory Disclosure in its Task Runner
## Impact
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.
## Patches
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.
## Workarounds
If upgrading is not immediately
OSV
n8n has In-Process Memory Disclosure in its Task Runner
osv·2026-03-25
CVE-2026-27496 [HIGH] n8n has In-Process Memory Disclosure in its Task Runner
n8n has In-Process Memory Disclosure in its Task Runner
## Impact
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.
## Patches
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.
## Workarounds
If upgrading is not immediately
No detection rules found.
No public exploits indexed.
2026-03-25
Published