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
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.
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 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.
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalFlowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromiumflowise, flowise-components
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- Criticaln8n Has an Arbitrary File Read via Git Noden8n, n8n, n8n
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- Criticaln8n has XML Node Prototype Pollution that to RCEn8n, n8n, n8n
- Criticaln8n has Prototype Pollution in XML Webhook Body Parser that Leads to RCEn8n, n8n, n8n
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.