CVE-2026-55608

In n8n-MCP prior to version 2.56.1, in HTTP mode with multi-tenancy enabled (ENABLE_MULTI_TENANT=true), local workflow version history backups were not isolated per tenant. This allowed an authenticated tenant to read and delete backups of other tenants, including full node definitions, credential references, and authorization headers.

n8n-MCP, an MCP server, has an authenticated server-side request forgery vulnerability affecting webhook trigger tools and the n8n API client. This issue exists in versions from 2.18.7 to before 2.50.2 and has been patched in version 2.50.2.

In n8n-MCP prior to 2.51.2, when ENABLE_MULTI_TENANT=true, HTTP requests without x-n8n-url or x-n8n-key headers silently fell back to the operator's credentials, allowing an authenticated MCP tenant to execute n8n management calls against the operator's instance instead of its own.

In n8n-MCP prior to 2.51.3, the workflow telemetry sanitizer could retain partial fragments of URL-shaped node parameters, such as customer identifiers or secrets in query strings, before sending data to the anonymous telemetry backend. This is fixed in version 2.51.3.

In n8n-MCP prior to version 2.47.13, when running in HTTP transport mode, authenticated tools/call requests had their full arguments and JSON-RPC params written to server logs before any redaction. When a tool call carries credential material (e.g., n8n_manage_credentials.data), raw values can be persisted in logs. In deployments with log collection, this can disclose bearer tokens, OAuth credentials, API keys, and other secrets. The issue requires authentication and is patched in version 2.47.13.

In n8n-MCP prior to version 2.47.11, when running in HTTP transport mode, request metadata for the POST /mcp endpoint was written to server logs regardless of authentication outcome. In deployments where logs are collected or forwarded, this can disclose bearer tokens, per-tenant API keys, and JSON-RPC payloads. Access control was not bypassed — unauthenticated requests were correctly rejected with 401 — but sensitive values could still be persisted in logs. The issue is patched in version 2.47.11.

n8n-MCP versions 2.47.4 through 2.47.13 have an incomplete URL validator in SSRFProtection.validateUrlSync() that lacks IPv6 checks. IPv4-mapped IPv6 addresses such as http://[::ffff:169.254.169.254] bypass cloud-metadata, localhost, and private-IP range checks, allowing an attacker to make the server issue requests to sensitive targets and return responses plus the x-n8n-api-key header. The issue is fixed in version 2.47.14.