Remote Code Execution (RCE) Affecting n8n-workflow package, versions >=1.0.0 <2.0.0-rc.1
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JS-N8NWORKFLOW-14723277
- published29 Dec 2025
- disclosed4 Dec 2025
- creditBerk Dedekargınoğlu, VladimirEliTokarev
Introduced: 4 Dec 2025
CVE-2025-68668 (opens in a new tab)How to fix?
Upgrade n8n-workflow to version 2.0.0-rc.1 or higher.
Overview
n8n-workflow is a Workflow base code of n8n
Affected versions of this package are vulnerable to Remote Code Execution (RCE) due to insufficient isolation in the Python Code Node that uses Pyodide. An authenticated attacker with permissions to create or modify workflows can execute arbitrary commands on the host system by creating or modifying workflows with malicious code.
Workaround
This vulnerability can be mitigated by:
Disabling the Code Node using the
NODES_EXCLUDEenvironment variable.Disabling Python support in the Code Node with
N8N_PYTHON_ENABLED=false.Configuring the task runner-based Python sandbox via the
N8N_RUNNERS_ENABLEDandN8N_NATIVE_PYTHON_RUNNERenvironment variables.