n8n-MCP: Incorrect authorization can expose default-scope workflow version backups in multi-tenant HTTP mode
CVE-2026-55608 · GHSA-2cf7-hpwf-47h9 · published 2026-07-14
- Severity
- Medium
- CVSS score
- 4.2
- Chance of exploitation (EPSS)
- 0.28%
- Fixed in
- 2.57.4
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
An authenticated MCP HTTP tenant could read or delete workflow-version backups stored in the default (single-tenant) scope — for example backups left from a prior single-tenant deployment or a migration period. Workflow snapshots may contain sensitive workflow configuration depending on their contents. Single-tenant and stdio deployments are not affected.
Upgrade n8n-mcp to 2.57.4 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.
2.57.4 Upgrade to n8n-mcp 2.57.4 or later. The fix requires a complete tenant context in multi-tenant mode and fails closed for workflow-version access that cannot be attributed to a specific tenant.
Restrict network access to the HTTP endpoint (firewall / reverse proxy / VPN) so only trusted callers can reach it. Run in stdio mode, which has no multi-tenant HTTP surface. If default-scope backups from a prior single-tenant deployment are not needed, removing them eliminates the exposure.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| n8n-mcp | npm | <= 2.57.3 | 2.57.4 |
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- Criticaln8n-MCP: Cross-tenant access to workflow version backups in multi-tenant HTTP deploymentsn8n-mcp
- Highn8n-MCP: Multi-tenant MCP requests fall back to process-level n8n credentials when tenant headers are absent or incompleten8n-mcp
- Highn8n-mcp affected by path traversal, redirect-following SSRF, and telemetry payload exposuren8n-mcp
- Highn8n-mcp webhook and API client paths has an authenticated SSRFn8n-mcp
- Highn8n-mcp's IPv4-mapped IPv6 addresses bypass SSRF protection in validateUrlSync(), enabling full SSRF for SDK embeddersn8n-mcp
- Highn8n-mcp has unauthenticated session termination and information disclosure in HTTP transportn8n-mcp
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.