n8n, an open source workflow automation platform, has a critical vulnerability identified as CVE-2025-68668. The flaw lies within the Python Code Node that uses Pyodide, affecting all versions from 1.0.0 to before 2.0.0. This vulnerability allows an authenticated user with permission to create or modify workflows to execute arbitrary commands on the host system running n8n, utilizing the same privileges as the n8n process. Given the potential impact of this vulnerability, organizations must take immediate action.
With a CVSS score of 9.9, this vulnerability is classified as critical. The high severity level underscores the necessity for organizations to prioritize patching immediately. The risk to organizations includes unauthorized command execution, which could lead to significant data breaches or system compromise.
Exploitability of this vulnerability is critical, with confirmed public exploit availability. Organizations using affected versions of n8n must act promptly to implement the patch found in version 2.0.0. Workarounds are also available which involve disabling the Code Node or Python support, but these should be considered temporary measures.
Security teams should assess their environments for this vulnerability and ensure that all instances of n8n are upgraded. The urgency for defenders is high due to the potential for widespread exploitation.
Vulnerability Details
The vulnerability allows for sandbox bypass within the Python Code Node of n8n, enabling arbitrary command execution. The CVSS vector indicates a network attack vector with low attack complexity, requiring low privileges and no user interaction. The scope of the attack changes from the vulnerable component to the host system. Both confidentiality and integrity impacts are rated high, while availability impact is low.
n8n has addressed this vulnerability in version 2.0.0, which is the recommended version for all users. The potential for exploitation necessitates that organizations assess their risk exposure and apply relevant patches.
Technical Analysis
The root cause of this vulnerability is a design flaw in the Python Code Node that fails to sufficiently isolate the execution environment. The attack vector is network-based, allowing attackers to exploit the flaw remotely. The attack complexity is low, requiring only authenticated access to create or modify workflows. Privileges required are also low, which increases the risk of exploitation.
User interaction is not required to exploit this vulnerability. The impacts on confidentiality and integrity are high, as attackers may gain unauthorized access to sensitive data and modify system behavior. However, the availability impact is low, meaning the system's uptime may not be significantly affected.
Risk & Impact Analysis
The real-world risk associated with this vulnerability is substantial. Organizations utilizing n8n should recognize the potential for significant data breaches or unauthorized system control. The blast radius of an attack could impact all workflows and data processed through the n8n instance, leading to severe operational disruptions.
Given the critical nature of this vulnerability, organizations should assess their environments for any instances of n8n version 1.x and prioritize their remediation efforts. The urgency assessment based on the CVSS score and active exploit availability indicates that this vulnerability should be addressed in priority patch cycles.
Exploitation Status
Signal | Status |
|---|---|
Known Exploit | Yes |
Public PoC | Yes |
Actively Exploited | No |
Ransomware Use | No |
Affected Versions
All versions of n8n from 1.0.0 to before 2.0.0 are affected by this vulnerability. Organizations must ensure they upgrade to version 2.0.0 or later to mitigate this risk. If version information is missing, organizations should assume all versions prior to vendor patch are vulnerable.
Mitigation & Remediation
To remediate this vulnerability, organizations should upgrade to n8n version 2.0.0 or later. If immediate patching is not feasible, workarounds include disabling the Code Node by setting the environment variable NODES_EXCLUDE to '["n8n-nodes-base.code"]', and disabling Python support by setting N8N_PYTHON_ENABLED to false. Configuration to use the task runner based Python sandbox can be accomplished via the N8N_RUNNERS_ENABLED and N8N_NATIVE_PYTHON_RUNNER environment variables.
Organizations should also implement network controls to restrict access to the n8n instance, monitor for suspicious activities, and conduct regular security assessments to identify and mitigate similar vulnerabilities in the future.
Detection Guidance
To detect potential exploitation of this vulnerability, organizations should monitor logs for unusual command execution patterns, especially those originating from the n8n Python Code Node. Behavioral anomalies indicating unauthorized access or modification of workflows should be flagged for review. Network signatures associated with command execution originating from n8n instances should also be established.
AppSecure Threat Intelligence Insight
The long-term significance of CVE-2025-68668 lies in its demonstration of potential weaknesses in the design of automation platforms like n8n. Security teams should take this as a lesson to enhance their security postures for both development and runtime environments.
As organizations increasingly rely on automation, the patterns observed in this vulnerability represent a growing trend in automated systems being targeted for exploitation. Continuous security testing and regular updates are essential to mitigate such risks.
Penetration testing should be integrated into security practices to ensure vulnerabilities are identified and addressed proactively.
Organizations can benefit from leveraging resources such as application security assessments to identify and remediate weaknesses ahead of potential exploitation.
In conclusion, organizations must recognize the critical nature of CVE-2025-68668 and apply necessary patches and mitigations to prevent exploitation.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
.webp)