n8n: Computer-use Shell Sandbox Not Enforced on Linux and Windows
n8n
- Severity
- Critical, CVSS 9.8
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Record
- CVE-2026-65590
- Affects
- n8n
- Known exploited
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- Record first published by the source
- July 22, 2026
- Source last modified
- October 24, 2026
Description
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.
Description quoted from the NVD record.
Who is affected
n8n is a tool for connecting apps and automating routine tasks. This flaw affects n8n versions before 2.29.8, and versions 2.30.x before 2.30.1, but only where the optional @n8n/computer-use package has been deliberately installed and is running. This package is an add-on that lets an automated agent run commands on a computer. Standard n8n installations are not affected. On Linux and Windows, the add-on does not apply its safety limits, so commands it runs can reach any file on the machine and the network without restriction. The limits only work on macOS. This flaw is rated Critical.
What to do
- The person who installed or runs n8n for your organization should check whether the
@n8n/computer-usepackage is installed and running. If it is not, this flaw does not affect you. - If the package is installed, update n8n to version
2.29.8, or to version2.30.1if you use the 2.30.x releases. - Give priority to computers running the package on Linux or Windows, since that is where the safety limits are missing.
- If an IT provider or vendor runs n8n for your organization, send them this advisory and ask when the update will be done.
Analysis written from the source record as of October 24, 2026 and reviewed before publishing.