n8n-mcp affected by path traversal, redirect-following SSRF, and telemetry payload exposure
GHSA-8g7g-hmwm-6rv2 · published 2026-05-08
- Severity
- High
- CVSS score
- 8.3
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 2.50.1
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 DISABLEDTOOLS). 2. Validated webhook, form, and chat trigger URLs followed redirects.
Upgrade n8n-mcp to 2.50.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.
Upgrade to n8n-mcp >= 2.50.1.
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 N8NMCPTELEMETRY_DISABLED=true in the environment before starting the server, or run npx n8n-mcp telemetry disable once.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| n8n-mcp | npm | < 2.50.1 | 2.50.1 |
- CriticalMCP Path Traversal Allows Full-Filesystem Read and JWT Secret Exfiltration Leading to Account Takeoverlangflow, langflow-base
- Critical@zereight/mcp-gitlab: Unauthenticated arbitrary file read via `upload_markdown` enables PAT exfiltration and full account takeover@zereight/mcp-gitlab
- CriticalFlowise RCE via SQL Database Chain Nodeflowise, flowise-components
- CriticalLangroid: SQLChatAgent dangerous-function blocklist can be bypassed with quoted or schema-qualified pg_read_file callslangroid
- Criticalfast-mcp-telegram: Bearer token path traversal bypasses reserved Telegram session protectionfast-mcp-telegram
- CriticalMCP Toolbox HTTP tool path parameters allow traversal to unintended endpointsgithub.com/googleapis/mcp-toolbox
- 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 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
- Highn8n-mcp has authenticated SSRF via instance-URL header in multi-tenant HTTP moden8n-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.