UTC
High

Shared-Workflow Editor Can Exfiltrate Credentials via Workflow Tool Node Inline Sub-Workflow

GHSA-4r56-g65c-fm83 · published 2026-08-19

Severity
High
CVSS score
7.2
Chance of exploitation (EPSS)
No CVE
Fixed in
2.36.2
What it is

n8n's credential check did not inspect the inline workflow JSON of every node type that executes an inline sub-workflow, so a reference to a credential the acting user does not hold was accepted and persisted, on both the workflow-update and workflow-creation paths. An editor on a shared workflow, or any user creating a workflow through the REST API, Public API, or MCP, could plant such a node; when the workflow was later executed under an identity that does hold the credential, the inline sub-workflow resolved the secret and could send it to an attacker-controlled endpoint. The credential was never shared with the attacker.

What to do

Upgrade n8n to 2.36.2 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

The issue has been fixed in n8n versions 2.35.4 and 2.36.2. Users should upgrade to one of these versions or later to remediate the vulnerability.

If you cannot upgrade yet

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 users on shared workflows. Restrict n8n instance access to fully trusted users only. Audit shared workflows for unexpected Workflow Tool nodes with inline sub-workflows referencing credentials not owned by the editor, and rotate any credentials that may have been exposed. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Affected
PackageRegistryAffectedFixed in
n8nnpm< 2.35.42.35.4
n8nnpm< 2.36.22.36.2

The impact, patch and workaround text comes from the advisory, shortened (published by n8n). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].