Server-side Request Forgery (SSRF) Affecting n8n-mcp package, versions <2.47.4
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-15954294
- published9 Apr 2026
- disclosed8 Apr 2026
- credityiğit ibrahim
Introduced: 8 Apr 2026
NewCVE-2026-39974 (opens in a new tab)How to fix?
Upgrade n8n-mcp to version 2.47.4 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 the instance-URL header in multi-tenant HTTP mode. An authenticated attacker can cause the server to issue HTTP requests to arbitrary URLs and read the response bodies by supplying crafted headers. This may allow access to internal network services, cloud metadata endpoints, or any host reachable by the server process.
Note: This is only exploitable if multi-tenant HTTP mode is enabled and the attacker possesses a valid authentication token.
Workaround
This vulnerability can be mitigated by implementing egress filtering at the network layer to block outbound traffic to internal ranges, disabling multi-tenant headers if not required, and restricting distribution of authentication tokens to trusted operators.