NPM · JULY 2026 · EARLY WARNING

Potential Shell Sandbox Bypass in @n8n/computer-use npm Package

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
GHSA-4V35-78JC-648RGHSA-FPG6-X68Q-5793Severity: HIGH

The @n8n/computer-use npm package before versions 2.29.8 and 2.30.1 reportedly does not enforce shell sandbox restrictions on Linux and Windows, potentially allowing unrestricted access to the host filesystem and network.

What happened

An early warning has been issued regarding the @n8n/computer-use npm package. Versions prior to 2.29.8 and 2.30.1 appear to have a vulnerability where shell sandbox restrictions are not enforced on Linux and Windows systems. This could allow unrestricted access to the host filesystem and network. The issue is under investigation, and it is recommended to upgrade to version 2.29.8 or later for Linux and Windows to mitigate potential risks. For more details, consult the primary sources provided.

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If @n8n/computer-use is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats