GHSA-cj9h-qx8g-pq2g: n8n Shared-Workflow Editor Can Exfiltrate Credentials Vulnerability

HIGH
Share
CWE-863
Published
Advisory Summary

GHSA-cj9h-qx8g-pq2g is a HIGH shared-workflow editor can exfiltrate credentials vulnerability (CWE-863: Incorrect Authorization) affecting n8n libraries in the npm ecosystem. The issue involves shared-workflow editor can exfiltrate credentials via inline sub-workflow json. Remediation is available by upgrading affected packages to version 1.123.67, 2.32.1, 2.31.5.

GHSA-cj9h-qx8g-pq2g at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-cj9h-qx8g-pq2g
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-863: Incorrect Authorization
Affected Product n8n
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-cj9h-qx8g-pq2g

To remediate this vulnerability, upgrade all affected n8n dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

n8n fixed: 1.123.67 
npm install n8n@1.123.67
n8n fixed: 2.32.1 
npm install n8n@2.32.1
n8n fixed: 2.31.5 
npm install n8n@2.31.5
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls n8n

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-cj9h-qx8g-pq2g, inspect your project dependencies using npm:

npm ls n8n

Analyze the terminal output to locate any version of n8n in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.123.67), your application is affected.

Note: The npm ls n8n command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. In n8n, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Impact n8n's credential-access checks validated only a node's top-level credentials, not credentials referenced inside an Execute Sub-workflow node's inline workflow JSON. A member with editor access to a shared workflow could reference a credential they were not permitted to use inside that inline JSON; it passed both save-time and runtime validation and resolved in the parent workflow's project context, letting the member use or exfiltrate a credential they could not otherwise access. Exploitation requires workflow sharing to be enabled and the attacker to have been explicitly granted Editor access to a shared workflow. The attacker must also know the target credential's ID. ## Patches The issue has been fixed in n8n versions 1.123.67, 2.31.5, and 2.32.1. Users should upgrade to one of these versions or later to remediate the vulnerability. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict workflow sharing to fully trusted users only, and avoid granting Editor access to untrusted members on workflows that use sensitive credentials. - Audit shared workflows for Execute Sub-workflow nodes with Source = "Parameter" and review their inline workflow definitions for unexpected credential references. - Restrict network egress from the n8n instance to prevent connections to attacker-controlled endpoints. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

GHSA-cj9h-qx8g-pq2g Affected n8n Versions

3 component(s)
Fixed Versions:
1.123.672.32.12.31.5
Product / Package Ecosystem Affected Versions Fixed Version
n8n
npm/n8n
npm
< 1.123.67
1.123.67
n8n
npm/n8n
npm
≥ 2.32.0
< 2.32.1
2.32.1
n8n
npm/n8n
npm
≥ 2.0.0-rc.0
< 2.31.5
2.31.5

References

GitHub Advisory / Wiki ADVISORY
https://github.com/n8n-io/n8n/security/advisories/GHSA-cj9h-qx8g-pq2g
Security Fix Commit FIX COMMIT
https://github.com/n8n-io/n8n/commit/f69dfc6dd2178a14ea1624d2e1d403c2e755042f
n8n Source Repository REPOSITORY
https://github.com/n8n-io/n8n
n8n Release RELEASE
https://github.com/n8n-io/n8n/releases/tag/n8n@1.123.67
n8n Release RELEASE
https://github.com/n8n-io/n8n/releases/tag/n8n@2.31.5
n8n Release RELEASE
https://github.com/n8n-io/n8n/releases/tag/n8n@2.32.1

Frequently Asked Questions

What is GHSA-cj9h-qx8g-pq2g?
GHSA-cj9h-qx8g-pq2g is a security vulnerability in n8n involving Shared-Workflow Editor Can Exfiltrate Credentials via Inline Sub-Workflow JSON under CWE-863: Incorrect Authorization.
Which n8n versions are affected?
Affected versions include releases prior to 1.123.67, 2.32.1, 2.31.5 across affected packages: n8n.
What version fixes GHSA-cj9h-qx8g-pq2g?
Upgrading to 1.123.67, 2.32.1, 2.31.5 (or the latest patched release for your respective branch) resolves the vulnerability.
Is n8n affected?
Yes, n8n is affected in releases prior to 1.123.67, 2.32.1, 2.31.5. Upgrade your dependency to 1.123.67, 2.32.1, 2.31.5 or later.
What CWE is associated with GHSA-cj9h-qx8g-pq2g?
GHSA-cj9h-qx8g-pq2g is classified under CWE-863: Incorrect Authorization (The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.).
How can I check npm dependencies for GHSA-cj9h-qx8g-pq2g?
Run the dependency tree command: 'npm ls n8n'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-cj9h-qx8g-pq2g",
  "modified" : "2026-07-22T22:11:22Z",
  "published" : "2026-07-22T22:11:22Z",
  "aliases" : [ ],
  "summary" : "n8n: Shared-Workflow Editor Can Exfiltrate Credentials via Inline Sub-Workflow JSON",
  "details" : "## Impact\n\nn8n's credential-access checks validated only a node's top-level credentials, not credentials referenced inside an Execute Sub-workflow node's inline workflow JSON. A member with editor access to a shared workflow could reference a credential they were not permitted to use inside that inline JSON; it passed both save-time and runtime validation and resolved in the parent workflow's project context, letting the member use or exfiltrate a credential they could not otherwise access.\n\nExploitation requires workflow sharing to be enabled and the attacker to have been explicitly granted Editor access to a shared workflow. The attacker must also know the target credential's ID.\n\n## Patches\n\nThe issue has been fixed in n8n versions 1.123.67, 2.31.5, and 2.32.1. Users should upgrade to one of these versions or later to remediate the vulnerability.\n\n## Workarounds\n\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Restrict workflow sharing to fully trusted users only, and avoid granting Editor access to untrusted members on workflows that use sensitive credentials.\n- Audit shared workflows for Execute Sub-workflow nodes with Source = \"Parameter\" and review their inline workflow definitions for unexpected credential references.\n- Restrict network egress from the n8n instance to prevent connections to attacker-controlled endpoints.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.123.67"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.32.0"
      }, {
        "fixed" : "2.32.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0-rc.0"
      }, {
        "fixed" : "2.31.5"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/security/advisories/GHSA-cj9h-qx8g-pq2g"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/commit/f69dfc6dd2178a14ea1624d2e1d403c2e755042f"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/n8n-io/n8n"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@1.123.67"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.31.5"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.32.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-863" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-22T22:11:22Z",
    "nvd_published_at" : null
  }
}