Path Traversal and Query Injection via the Supabase Node Table Name
GHSA-rqch-9jrh-cr8w · published 2026-09-16
- Severity
- High
- CVSS score
- 7.1
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 2.40.1
The Supabase node inserted the tableId parameter into the request path without validation, and the parameter accepts expressions, so it could be bound to untrusted input. A traversal sequence reached Supabase's Auth and Storage APIs carrying the administrative serviceRole key, which bypasses Row Level Security; a query separator let injected text widen column projections and row filters, including on update and delete. All five row operations are affected. Only workflows that bind tableId to untrusted input are exploitable.
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 using the Supabase node and ensure the table name parameter is not bound to an expression referencing external or untrusted input. Disable the Supabase node by adding n8n-nodes-base.supabase to the NODES_EXCLUDE environment variable if it is not required. Rotate the Supabase serviceRole key for any instance where a vulnerable workflow configuration may have been exposed. 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.