Am I affected by n8n: computer-use Shell Sandbox Not Enforced on Linux and Windows? What should I do?
The shell tool in the
@n8n/computer-usepackage applied its sandbox restrictions only on macOS.Affected: n8n < 2.29.8 and >= 2.30.0, < 2.30.1. Fixed in: 2.29.8 and 2.30.1. What should you check, and what should you do about it?
Full incident page with sources: https://agentarmorhq.com/incidents/2026/07/cve-2026-65590-n8n-n8n-computer-use (opens external site)
1 answer
Am I affected? Affected: n8n < 2.29.8 and >= 2.30.0, < 2.30.1. Fixed in: 2.29.8 and 2.30.1.
- Check your version: run
npm ls n8n. Versions >= 2.30.0, < 2.30.1 of n8n are affected.
What to do now
- Upgrade to the fixed version: run
npm install n8n@2.30.1(first patched version 2.30.1). - Upgrade to n8n 2.29.8 or 2.30.1 or later.
- Disable or avoid deploying the
@n8n/computer-usepackage 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.
General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.
Sources
- GitHub Advisory Database: https://github.com/advisories/GHSA-fpg6-x68q-5793 (opens external site)
Full incident page: https://agentarmorhq.com/incidents/2026/07/cve-2026-65590-n8n-n8n-computer-use (opens external site)
Did this work for you?- Check your version: run