In multi-tenant HTTP mode, n8n-mcp versions up to 2.57.3 have an authorization flaw allowing an authenticated tenant to access or delete workflow-version backups in the default single-tenant scope. This exposure affects local backup storage from prior single-tenant deployments or migration periods and may reveal sensitive workflow configurations. Single-tenant and stdio mode deployments are not impacted. The issue is fixed in version 2.57.4.
CVE-2026-54052 is a critical vulnerability in n8n-mcp affecting multi-tenant HTTP deployments up to version 2.56.0. It allows authenticated tenants to access and manipulate workflow version backups belonging to other tenants due to lack of isolation. These backups contain sensitive node definitions including credential references, posing confidentiality, integrity, and availability risks. The issue is fixed in version 2.56.1 by isolating stored version history per tenant instance.
A vulnerability in n8n-mcp's multi-tenant HTTP mode allows authenticated tenants to cause requests missing required tenant headers to fall back to the operator's own n8n instance credentials. This can lead to unauthorized access to the operator's workflows, executions, data, and credentials, and potentially remote code execution if code-node execution is permitted. The issue affects multi-tenant deployments with ENABLE_MULTI_TENANT=true and is fixed in n8n-mcp 2.51.3.
A vulnerability in n8n-mcp versions from 2.14.1 up to but not including 2.51.3 allows partial fragments of URL-shaped node parameters to be retained in workflow telemetry data sent to the anonymous telemetry backend. This may expose sensitive information such as customer or tenant identifiers and short secrets embedded in query strings. The issue does not affect credentials, OAuth tokens, or workflow execution data. The vulnerability is fixed in version 2.51.3. Users unable to upgrade immediately can disable telemetry via environment variables.
CVE-2026-44694 is an authenticated Server-Side Request Forgery (SSRF) vulnerability in n8n-mcp affecting webhook trigger tools, the n8n API client, and URLs supplied via the x-n8n-url header in multi-tenant HTTP mode. An attacker with MCP session access can make HTTP requests from the n8n-mcp host to internal services and cloud metadata endpoints, potentially exfiltrating sensitive credentials. The vulnerability affects multi-tenant and single-tenant deployments, as well as stdio deployments via prompt injection. The issue is fixed in n8n-mcp version 2.50.2.
A Server-Side Request Forgery (SSRF) vulnerability exists in the n8n-mcp SDK embedder path versions 2.47.4 through 2.47.13. The synchronous URL validator in SSRFProtection.validateUrlSync() fails to check IPv4-mapped IPv6 addresses, allowing bypass of protections against cloud metadata, localhost, and private IP ranges. An attacker controlling the n8nApiUrl parameter can cause the server to make HTTP requests to internal or cloud metadata endpoints and receive response data, with the n8nApiKey header forwarded to the attacker-controlled target. This vulnerability is fixed in version 2.47.14.
n8n-mcp versions 2.14.1 up to but not including 2.47.13 running in HTTP transport mode log sensitive tool-call arguments including credential material such as bearer tokens, OAuth credentials, API keys, and webhook authentication headers. This logging occurs before any redaction, potentially exposing secrets in server logs accessible beyond the request trust boundary. The vulnerability requires authentication and is mitigated in stdio transport mode. A fix is available in version 2.47.13 that prevents logging sensitive values by summarizing arguments without recording raw data.
A vulnerability in n8n-mcp versions 2.14.1 through 2.47.10 allows sensitive request data to be logged on unauthorized POST /mcp HTTP requests. This includes bearer tokens, per-tenant API keys, and JSON-RPC payloads. Although unauthorized requests are rejected, sensitive information is still recorded in server logs, potentially exposing it if logs are accessible outside the trusted boundary. The issue affects deployments using HTTP transport mode and is fixed in version 2.47.11.
An authenticated Server-Side Request Forgery (SSRF) vulnerability exists in n8n-mcp versions up to 2.47.3. An attacker with a valid AUTH_TOKEN can cause the server to make HTTP requests to arbitrary URLs via multi-tenant HTTP headers, potentially accessing sensitive internal resources such as cloud metadata endpoints and internal network services. The issue affects multi-tenant HTTP deployments and is fixed in version 2.47.4.
### Summary
Several HTTP transport endpoints in n8n-mcp lacked proper authentication, and the health check endpoint exposed sensitive operational metadata without credentials.
### Impact
An unauthenticated attacker with network access to the n8n-mcp HTTP server could disrupt active MCP sessions and gather information useful for further attacks.
### Patches
Fixed in **v2.47.6**. All MCP session endpoints now require Bearer authentication. The health check endpoint has been reduced to a minimal liveness response.
### Workarounds
If you cannot upgrade immediately:
- **Restrict network access** to the HTTP server using firewall rules, reverse proxy IP allowlists, or a VPN so that only trusted clients can reach it.
- **Use stdio mode** (`MCP_MODE=stdio`) instead of HTTP mode. The stdio transport does not expose any HTTP endpoints and is unaffected by this vulnerability.
Upgrading to v2.47.6 is still strongly recommended.
### Credit
Reported by @yotampe-pluto.
## Impact
`n8n-mcp` versions before 2.50.1 contained three independently-reported issues affecting deployments that run the n8n API integration:
1. **Caller-supplied identifiers were not validated before being used as URL path segments** by the n8n API client. An authenticated MCP caller passing a crafted workflow id could cause outbound requests carrying the configured n8n API key to land on other same-origin endpoints, bypassing handler-level access controls (including `DISABLED_TOOLS`).
2. **Validated webhook, form, and chat trigger URLs followed redirects.** A URL that passed initial validation could redirect the outbound request to a host that would otherwise have been rejected, with the response body returned to the caller. Reachable as non-blind SSRF over authenticated MCP calls.
3. **Mutation telemetry stored unredacted operation payloads.** On instances running with the default opt-in telemetry, partial-update operation diffs were uploaded without redaction. Operation values can carry the same node-parameter values the workflow contains, including bearer tokens, API keys, and webhook secrets.
## Severity
CVSS 8.3 (HIGH). Exploitation requires an authenticated MCP caller and an n8n API integration configured with an n8n API key.
## Patched versions
Upgrade to `n8n-mcp >= 2.50.1`.
## Workarounds
- For issues (1) and (2): restrict network access to the HTTP transport (firewall, reverse-proxy ACL, or VPN) so only trusted callers can reach the MCP HTTP port; or switch to stdio mode, which exposes no HTTP surface for these issues.
- For issue (3): set `N8N_MCP_TELEMETRY_DISABLED=true` in the environment before starting the server, or run `npx n8n-mcp telemetry disable` once.
## Credit
Reported by @cybercraftsolutionsllc.