A significant security flaw has been discovered in n8n, a popular open-source platform for automating workflows. This vulnerability could allow an attacker to take control of the system by running malicious code.
Specifically, if an authenticated user has the ability to create or change workflows that use a Python Code Node, they could break out of the usual security restrictions, known as a sandbox. This escape would grant them the power to execute any code they wish on the container that runs tasks. It’s important to note that this issue only affects n8n installations where the Python Task Runner feature is turned on.
CVE Details
- Product: n8n (Workflow Automation Platform)
- Published Date: June 23, 2026
- Severity: High
- Status: Analyzed
Affected Products
The n8n workflow automation platform is vulnerable in versions prior to:
- 1.123.48
- 2.21.8
- 2.22.4
Users running any version older than these specified patches are at risk.
Current Status
This vulnerability has been officially analyzed and confirmed.
Severity Level
The vulnerability is rated as High severity with a CVSS score of 8.5 (CVSS v3.1). The CVSS v4 score is also provided as 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. This high rating reflects the significant risk, as an attacker with low privileges can achieve high confidentiality impact and low integrity impact on the vulnerable system without user interaction or complex attack methods, provided the Python Task Runner is enabled.
Possible Solutions
The good news is that fixes are available. To protect your n8n installation, it is crucial to update to a patched version immediately.
- Upgrade: The vulnerability is resolved in n8n versions 1.123.48, 2.21.8, and 2.22.4. Updating to any of these versions or newer will secure your system.
If an immediate upgrade isn’t feasible, consider these temporary workarounds:
- Limit Permissions: Restrict the ability to create or modify workflows to only users you fully trust. This limits who can exploit the flaw.
- Disable Python Code Node: You can disable the problematic Python Code node by setting the environment variable
NODES_EXCLUDEto includen8n-nodes-base.code. Alternatively, you can disable the entire Python Task Runner.
Please remember that these workarounds offer only temporary protection and do not fully eliminate the risk. Prioritize upgrading to a patched version as soon as possible.
References
- https://github.com/n8n-io/n8n/security/advisories/GHSA-9pq8-m8gp-4p53
