CVE-2026-65590: n8n before 2.30.1 Shell Sandbox Bypass on Linux Windows
Impact The shell tool in the @n8n/computer-use package applied its sandbox restrictions only on macOS. On Linux and Windows, shell commands executed by the tool ran without any filesystem or network restrictions, allowing unrestricted access to the host filesystem and network from within the computer-use agent process.
This issue only affects deployments where the @n8n/computer-use package is explicitly installed and running. It does not affect standard n8n installations.
Patches The issue has been fixed in n8n versions 2.29.8 and 2.30.1. Users should upgrade to one of these versions or later to remediate the vulnerability.
The fix adds sandbox enforcement on Linux via bubblewrap and disables the shell tool entirely when a working sandbox cannot be established. An explicit opt-out flag (--dangerously-disable-shell-sandbox) is available for deployments that require unsandboxed shell access and accept the associated risk.
Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Disable or avoid deploying the @n8n/computer-use package on Linux or Windows hosts until the fix is applied. - Restrict access to the n8n instance and the computer-use agent to fully trusted users only.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Other sources
n8n before 2.29.8 and 2.30.x before 2.30.1 does not enforce shell sandbox restrictions on Linux and Windows in the @n8n/computer-use package (sandboxing was applied only on macOS). Shell commands executed by the tool run without any filesystem or network restrictions, allowing unrestricted access to the host filesystem and network from within the computer-use agent process. This issue only affects deployments where the @n8n/computer-use package is explicitly installed and running; standard n8n installations are not affected.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.29.8 - Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.30.1 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.29.8 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.30.1 - Configuration
Disable or avoid deploying the `@n8n/computer-use` package on Linux or Windows hosts until the fix is applied.
n8n (@n8n/computer-use package) @n8n/computer-use deployment = disabled - Compensating control
Restrict access to the n8n instance and the computer-use agent to fully trusted users only.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-65590?
CVE-2026-65590 has a medium severity level with a CVSS score of 5.5.
How do I fix CVE-2026-65590?
To fix CVE-2026-65590, upgrade to n8n version 2.30.1 or later.
What impact does CVE-2026-65590 have?
CVE-2026-65590 allows unrestricted access to the host filesystem and network on Linux and Windows due to inadequate sandbox restrictions.
Which software is affected by CVE-2026-65590?
CVE-2026-65590 affects the n8n tool, specifically the `@n8n/computer-use` package.
Is CVE-2026-65590 related to OS Command Injection?
Yes, CVE-2026-65590 is classified under OS Command Injection vulnerabilities.