How severe is GHSA-vpcf-gvg4-6qwr?

GHSA-vpcf-gvg4-6qwr has a CVSS score of 9.9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-vpcf-gvg4-6qwr?

GHSA-vpcf-gvg4-6qwr affects the following packages: n8n (npm), n8n (npm), n8n (npm). Ecosystems affected: npm.

How do I fix GHSA-vpcf-gvg4-6qwr?

Update n8n to 1.123.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vpcf-gvg4-6qwr is resolved across your whole dependency graph.

How do I detect GHSA-vpcf-gvg4-6qwr 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-vpcf-gvg4-6qwr 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-vpcf-gvg4-6qwr actively exploited in the wild?

No public exploit code has been indexed for GHSA-vpcf-gvg4-6qwr 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-vpcf-gvg4-6qwr?

GHSA-vpcf-gvg4-6qwr has an EPSS (Exploit Prediction Scoring System) score of 10.7%, placing it in the 96th 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 warrants monitoring and prompt remediation.

What type of vulnerability is GHSA-vpcf-gvg4-6qwr?

GHSA-vpcf-gvg4-6qwr is classified as Code Injection (CWE-94). 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-vpcf-gvg4-6qwr published, and has it been updated?

GHSA-vpcf-gvg4-6qwr was published on February 25, 2026 and was last updated on February 28, 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

CRITICAL severity

n8n: Expression Sandbox Escape Leads to RCEGHSA-vpcf-gvg4-6qwr

CRITICALFix: n8n-io/n8n@1479aab

GHSA-vpcf-gvg4-6qwr is a critical-severity (CVSS 9.9) Code Injection vulnerability in n8n. EPSS puts its 30-day exploitation probability at 10.7% (96th percentile). A fix is available for n8n — see the affected versions and patch details below.

Also known asCVE-2026-27577

Published

Feb 25, 2026

Updated

Feb 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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-vpcf-gvg4-6qwr.

EPSS Exploitation Probability

via FIRST.org ↗

10.7%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 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

150Kdownloads / week

Description

Impact

Additional exploits in the expression evaluation of n8n have been identified and patched following CVE-2025-68613. An authenticated user with permission to create or modify workflows could abuse crafted expressions in workflow parameters to trigger unintended system command execution on the host running n8n.

Patches

The issues have been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to one of these versions or later to remediate all known vulnerabilities.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

Limit workflow creation and editing permissions to fully trusted users only.
Deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Resources

Best practices for securing n8n
Initial vulnerability advisory: CVE-2025-68613

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`n8n`	all versions	1.123.22`npm install n8n@1.123.22`
📦npm	`n8n`	≥ 2.0.0&&< 2.9.3	2.9.3`npm install n8n@2.9.3`
📦npm	`n8n`	≥ 2.10.0&&< 2.10.1	2.10.1`npm install n8n@2.10.1`

Affected Products

1 product · 3 configurations

Application

n8nn8n

≥ 2.10.0 && < 2.10.1

range

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 1.123.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vpcf-gvg4-6qwr 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 Additional exploits in the expression evaluation of n8n have been identified and patched following [CVE-2025-68613](https://github.com/n8n-io/n8n/security/advisories/GHSA-v98v-ff95-f3cp). An authenticated user with permission to create or modify workflows could abuse crafted expressions in workflow parameters to trigger unintended system command execution on the host running n8n. ## Patches The issues have been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to one of these versions or later to remediate all known vulnerabilities. ## Workarounds If upgradin