Server-side Request Forgery (SSRF) Affecting n8n-mcp package, versions >=2.18.7 <2.50.2
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-16635404
- published11 May 2026
- disclosed8 May 2026
- creditfg0x0
Introduced: 8 May 2026
NewCVE-2026-44694 (opens in a new tab)How to fix?
Upgrade n8n-mcp to version 2.50.2 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) in the N8nApiClient, when handling webhook triggers, API client base URLs, and per-request URLs supplied via the x-n8n-url header in multi-tenant HTTP mode. An attacker who can control tool calls can enumerate internal services and expose stored secrets. This is only exploitable if the attacker has a valid MCP session or can influence tool arguments in single-tenant or stdio deployments.
Note: The fix for this vulnerability introduces WEBHOOK_SECURITY_MODE, which must be explicitly changed from its default value of strict if an operator is connecting to localhost or an RFC1918 address.
Workaround
This vulnerability can be mitigated by restricting network egress from the host using a firewall, reverse proxy, or cloud security group to deny access to cloud metadata IPs (169.254.169.254, 169.254.170.2, 100.100.100.200, 192.0.0.192, metadata.google.internal) and unnecessary RFC1918 networks, or running in stdio mode if multi-tenant surface is not needed, or disabling workflow management tools if not required.