UTC
High

Path Traversal in the n8n Node Redirects Public API Calls to Unintended Resources

GHSA-89p4-6h98-c7xm · published 2026-09-16

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

The built-in n8n node built its Public API request paths from a caller-supplied resource id without encoding or validating it, so a crafted id could redirect the call to a different resource while still using the stored API key. Where a workflow binds that id to untrusted input, an unauthenticated caller could read, modify or delete workflows and executions outside the intended scope, and reach a credential's secret by repointing a live workflow. Impact stays within the resource types the key already has scope for.

What to do

Upgrade n8n to 2.40.1 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 1.123.80, 2.39.6, and 2.40.1. 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 n8n instance access to fully trusted users only. Audit all workflows that use the n8n node and ensure that ID fields are not bound to expressions sourced from untrusted or externally supplied input. Restrict or disable public webhook endpoints that feed into workflows using the n8n node until the instance is patched. Review and rotate any API credentials that may have been exposed via workflows using the n8n node with expression-bound ID fields. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Affected
PackageRegistryAffectedFixed in
n8nnpm< 1.123.801.123.80
n8nnpm< 2.39.62.39.6
n8nnpm< 2.40.12.40.1

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].