Which versions of n8n are affected by CVE-2026-42234?

CVE-2026-42234 is a sandbox escape vulnerability in n8n's Python Task Runner that allows authenticated workflow editors to execute arbitrary code on the task runner container.. A patch is available.

How to fix or mitigate CVE-2026-42234?

Within 24 hours: inventory all n8n instances and confirm Python Code Node enablement status. Within 7 days: upgrade affected instances to vendor-released patch versions 1.123.32, 2.17.4, or 2.18.1 (select based on current major version). Within 30 days: conduct access review of workflow editor role assignments and implement principle of least privilege for workflow creation/modification permissions.

n8n CVE-2026-42234

Q: What is the CVSS score of CVE-2026-42234?

CVE-2026-42234 has a CVSS 4.0 base score of 7.1 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/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 exploitation probability: 0.1%.

EUVD-2026-27109 HIGH

Code Injection (CWE-94)

2026-04-29 https://github.com/n8n-io/n8n

GHSA-44v6-jhgm-p3m4

RCE Python Code Injection

7.1

CVSS 4.0 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

7.1 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/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

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

May 04, 2026 - 20:01 EUVD

Re-analysis Queued

May 04, 2026 - 19:22 vuln.today

cvss_changed

CVSS changed

May 04, 2026 - 19:22 NVD

7.5 (HIGH) 7.1 (HIGH)

Source Code Evidence Fetched

Apr 29, 2026 - 22:01 vuln.today

Analysis Generated

Apr 29, 2026 - 22:01 vuln.today

Analysis Generated

Apr 29, 2026 - 21:30 vuln.today

CVE Published

Apr 29, 2026 - 21:21 nvd

HIGH 7.5

DescriptionGitHub Advisory

Impact

An authenticated user with permission to create or modify workflows containing a Python Code Node could escape the sandbox and achieve arbitrary code execution on the task runner container.

This issue only affects instances where the Python Task Runner is enabled.

Patches

The issue has been fixed in n8n versions 1.123.32, 2.17.4, and 2.18.1. Users should upgrade to one of these versions or later to remediate the vulnerability.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

Limit workflow creation and editing permissions to fully trusted users only.
Disable the Python Code node by adding n8n-nodes-base.code to the NODES_EXCLUDE environment variable, or disable the Python Task Runner entirely.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

AnalysisAI

Sandbox escape in n8n's Python Task Runner enables authenticated workflow editors to execute arbitrary code on the task runner container. This vulnerability (CWE-94: Improper Control of Generation of Code) affects n8n instances with the Python Code Node feature enabled, allowing attackers with workflow creation/modification permissions to break out of the Python sandbox. Vendor-released patches are available in versions 1.123.32, 2.17.4, and 2.18.1. No public exploit identified at time of analysis, though the technical details in the GitHub advisory provide sufficient information for exploitation by authenticated users.

Technical ContextAI

n8n is a workflow automation platform (npm package n8n) that includes a Python Code Node for executing Python scripts within workflows. The Python Task Runner executes this code in a sandboxed container environment to prevent unauthorized system access. This vulnerability (CWE-94: Improper Control of Generation of Code / Code Injection) represents a sandbox escape flaw in the Python Task Runner implementation. The affected component allows authenticated users to bypass sandbox restrictions through crafted Python code within workflow nodes, achieving arbitrary code execution at the container level. The vulnerability is specific to the Python Task Runner feature - installations not using this feature or those with the Python Code node disabled are not affected. The affected npm package versions span three release branches: legacy 1.x (< 1.123.32), and current 2.x branches (2.17.0-2.17.3 and 2.18.0).

RemediationAI

Upgrade n8n to a patched version immediately: version 1.123.32 for users on the 1.x branch, version 2.17.4 for those on 2.17.x, or version 2.18.1 for those on 2.18.x or later. Vendor-released patches are confirmed in these versions per GitHub advisory GHSA-44v6-jhgm-p3m4. If immediate upgrade is not feasible, implement compensating controls with awareness of their limitations: restrict workflow creation and editing permissions to only fully trusted administrators (reduces attack surface but increases operational friction and may conflict with legitimate use cases), disable the Python Code node by adding n8n-nodes-base.code to the NODES_EXCLUDE environment variable (eliminates Python execution capability but breaks workflows dependent on Python nodes), or disable the Python Task Runner entirely via configuration (same impact as disabling the node). The vendor explicitly states these workarounds 'do not fully remediate the risk' and should only be temporary measures. Organizations should audit existing workflows for suspicious Python code during the remediation window, review user accounts with workflow edit permissions, and monitor task runner container logs for unusual activity. No other mitigations fully address the sandbox escape without patching.