Summary
Workarounds
Administrators can disable the Execute Command node by setting the following environment variable before starting n8n:
export NODES_EXCLUDE: "[\"n8n-nodes-base.executeCommand\"]"
References
n8n docs: Execute Command
n8n docs: Blocking nodes
Impact
The Execute Command node in n8n allows execution of arbitrary commands on the host system where n8n runs. While this functionality is intended for advanced automation and can be useful in certain workflows, it poses a security risk if all users with access to the n8n instance are not fully trusted.
An attacker, either a malicious user or someone who has compromised a legitimate user account, could exploit this node to run arbitrary commands on the host machine, potentially leading to data exfiltration, service disruption, or full system compromise.
This vulnerability affects all n8n deployments where:
- The
Execute Commandnode is enabled, and - Not all user accounts are strictly controlled and trusted.
n8n.cloud is not impacted.
Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.
GHSA-365G-VJW2-GRX8 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
No code changes have been made to alter the behavior of the Execute Command node. The recommended mitigation is to disable the node by default in environments where it is not explicitly required.
Future n8n versions may change the default availability of this node.
Frequently Asked Questions
- What is GHSA-365G-VJW2-GRX8? GHSA-365G-VJW2-GRX8 is a high-severity OS command injection vulnerability in n8n-nodes-base (npm), affecting versions <= 1.113.0. No fixed version is listed yet. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
- How severe is GHSA-365G-VJW2-GRX8? GHSA-365G-VJW2-GRX8 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by GHSA-365G-VJW2-GRX8?
n8n-nodes-base(npm) (versions <= 1.113.0)n8n(npm) (versions <= 1.114.4)
- Is there a fix for GHSA-365G-VJW2-GRX8? No fixed version is listed for GHSA-365G-VJW2-GRX8 yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is GHSA-365G-VJW2-GRX8 exploitable, and should I be worried? Whether GHSA-365G-VJW2-GRX8 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-365G-VJW2-GRX8 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-365G-VJW2-GRX8? No fixed version is listed yet. In the interim: Avoid passing untrusted input to shell commands. Use parameterized APIs or libraries that do not invoke a shell.