Server-side Request Forgery (SSRF) Affecting n8n-mcp package, versions <2.50.1
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-N8NMCP-16624718
- published10 May 2026
- disclosed8 May 2026
- creditcybercraftsolutionsllc
Introduced: 8 May 2026
New CVE NOT AVAILABLE CWE-22 (opens in a new tab)How to fix?
Upgrade n8n-mcp to version 2.50.1 or higher.
Overview
n8n-mcp is an Integration between n8n workflow automation and Model Context Protocol (MCP)
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via improper validation of caller-supplied identifiers and redirect handling in the API integration process. An attacker can access sensitive information, bypass access controls, and trigger outbound requests to unintended endpoints by supplying crafted workflow IDs or URLs, and may also cause unredacted operation payloads containing secrets to be stored and exposed through telemetry. This is only exploitable if the deployment is configured with an n8n API key and the attacker is an authenticated MCP caller.
Workaround
This vulnerability can be mitigated by restricting network access to the HTTP transport (using firewall, reverse-proxy ACL, or VPN), switching to stdio mode to eliminate the HTTP surface, or disabling telemetry by setting the environment variable N8N_MCP_TELEMETRY_DISABLED=true or running 'npx n8n-mcp telemetry disable'.