Cyber Resilience

CVE-2026-27496

N8N ≤ 1.123.22

Published
25 March 2026
Modified
27 March 2026
Patch / advisory
CVSS Score v4 7.1
Click a component to see what it means
Raw vectorCVSS: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
EPSS Score 0.0026 18th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-27496 is a high-severity Use of Uninitialized Resource (CWE-908) vulnerability in N8N N8N. Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-6 (Least Privilege) and SC-39 (Process Isolation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1528 Steal Application Access Token Credential Access
Adversaries can steal application access tokens as a means of acquiring credentials to access remote systems and resources.
Why these techniques?

Vulnerability enables direct memory disclosure of residual secrets/tokens via JS Task Runner, facilitating data collection from local process and theft of application access tokens.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-54311Same product: N8N N8N
CVE-2026-42226Same product: N8N N8N
CVE-2026-54304Same product: N8N N8N
CVE-2026-54305Same product: N8N N8N
CVE-2026-59209Same product: N8N N8N
CVE-2026-56348Same product: N8N N8N
CVE-2026-49465Same product: N8N N8N
CVE-2026-33720Same product: N8N N8N
CVE-2026-33660Same product: N8N N8N
CVE-2026-45732Same product: N8N N8N

Affected Assets

n8n
n8n
2.10.0 · ≤ 1.123.22 · 2.0.0 — 2.9.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
Detect
Catch it (NIST detect / respond)
  • SI-2 Flaw Remediation
Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces the documented mitigation of restricting workflow creation and editing permissions to only fully trusted users, preventing untrusted actors from invoking the vulnerable Task Runner path.

prevent

Requires process isolation so that the JavaScript Task Runner executes in a separate address space (external runner mode), limiting residual memory disclosure to the isolated runner process only.

respondrecover

Mandates timely application of the vendor patches (1.123.22/2.9.3/2.10.1) that eliminate the uninitialized-buffer allocation flaw in the Task Runner.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC activities such as static analysis and code review directly prevent use of uninitialized resources while also addressing many other weaknesses.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing in development and acceptance can detect uninitialized resource usage through dynamic analysis and fuzzing.

prevents

Secure development life cycle mandates initialization checks and static analysis that can catch uninitialized resource use.

prevents

Application security requirements can specify mandatory initialization of variables and resources before use.

prevents

Secure system architecture and engineering principles include defensive coding practices that prevent use of uninitialized memory or objects.

prevents

Secure coding standards directly require explicit initialization of all variables and resources, substantially mitigating CWE-908.

References