https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 10 Oct 2026 15:23:16 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-339306 EUVD-2026-339306 https://cve.radiocsirt.org/vuln/euvd-2026-339306 https://cve.radiocsirt.org/vuln/fkie_cve-2026-65590 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-65590 https://cve.radiocsirt.org/vuln/ghsa-fpg6-x68q-5793 <p><strong>Affected:</strong> npm: n8n</p> <p>## 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.</p> <p>This issue only affects deployments where the `@n8n/computer-use` package is explicitly installed and running. It does not affect standard n8n installations.</p> <p>## 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.</p> <p>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.</p> <p>## 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.</p> <p>These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.</p> <p><strong>Affected:</strong> npm: n8n</p> <p>## 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.</p> <p>This issue only affects deployments where the `@n8n/computer-use` package is explicitly installed and running. It does not affect standard n8n installations.</p> <p>## 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.</p> <p>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.</p> <p>## 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.</p> <p>These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.</p> https://cve.radiocsirt.org/vuln/ghsa-fpg6-x68q-5793