How severe is GHSA-fpg6-x68q-5793?

No CVSS score has been assigned to GHSA-fpg6-x68q-5793 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fpg6-x68q-5793?

GHSA-fpg6-x68q-5793 affects the following packages: n8n (npm), n8n (npm). Ecosystems affected: npm.

How do I fix GHSA-fpg6-x68q-5793?

Update n8n to 2.30.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fpg6-x68q-5793 is resolved across your whole dependency graph.

How do I detect GHSA-fpg6-x68q-5793 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-fpg6-x68q-5793 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-fpg6-x68q-5793 actively exploited in the wild?

No public exploit code has been indexed for GHSA-fpg6-x68q-5793 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-fpg6-x68q-5793?

GHSA-fpg6-x68q-5793 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 47th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-fpg6-x68q-5793?

GHSA-fpg6-x68q-5793 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-fpg6-x68q-5793 published, and has it been updated?

GHSA-fpg6-x68q-5793 was published on July 22, 2026 and was last updated on July 22, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

n8n: computer-use Shell Sandbox Not Enforced on Linux and WindowsGHSA-fpg6-x68q-5793

GHSA-fpg6-x68q-5793 is a OS Command Injection vulnerability in n8n. A fix is available for n8n — see the affected versions and patch details below.

Also known asCVE-2026-65590

Published

Jul 22, 2026

Updated

Jul 22, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-fpg6-x68q-5793.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

36other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

n8nnpm

80Kdownloads / week

Description

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`n8n`	≥ 2.30.0&&< 2.30.1	2.30.1`npm install n8n@2.30.1`
📦npm	`n8n`	all versions	2.29.8`npm install n8n@2.29.8`

Affected Products

1 product · 4 configurations

Application

n8nn8n

< 2.29.8

1 version

2.30.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update n8n to 2.30.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fpg6-x68q-5793 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

## 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 versio

O3 Security · Impact-Aware SCA

Is GHSA-fpg6-x68q-5793 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

n8n: computer-use Shell Sandbox Not Enforced on Linux and WindowsGHSA-fpg6-x68q-5793

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

Real-World Exposure

Description

Impact

Patches

Workarounds

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-fpg6-x68q-5793 in your dependencies?