n8n-mcp 2.47.2

Direct Vulnerabilities

Known vulnerabilities in the n8n-mcp package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free

Vulnerability	Vulnerable Version
H Missing Authentication for Critical Function n8n-mcp is an Integration between n8n workflow automation and Model Context Protocol (MCP) Affected versions of this package are vulnerable to Missing Authentication for Critical Function due to missing authentication in several HTTP transport endpoints and exposure of sensitive operational metadata in the health check endpoint. An attacker can terminate active sessions and obtain information useful for further attacks by sending unauthenticated requests to the affected endpoints. How to fix Missing Authentication for Critical Function? Upgrade `n8n-mcp` to version 2.47.6 or higher.	<2.47.6
H Server-side Request Forgery (SSRF) 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. How to fix Server-side Request Forgery (SSRF)? Upgrade `n8n-mcp` to version 2.47.4 or higher.	<2.47.4

Vulnerability

Vulnerable Version

Missing Authentication for Critical Function

n8n-mcp is an Integration between n8n workflow automation and Model Context Protocol (MCP)

Affected versions of this package are vulnerable to Missing Authentication for Critical Function due to missing authentication in several HTTP transport endpoints and exposure of sensitive operational metadata in the health check endpoint. An attacker can terminate active sessions and obtain information useful for further attacks by sending unauthenticated requests to the affected endpoints.

How to fix Missing Authentication for Critical Function?

Upgrade n8n-mcp to version 2.47.6 or higher.

<2.47.6

Server-side Request Forgery (SSRF)

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.

How to fix Server-side Request Forgery (SSRF)?

Upgrade n8n-mcp to version 2.47.4 or higher.

<2.47.4

n8n-mcp@2.47.2

Integration between n8n workflow automation and Model Context Protocol (MCP)

latest version

latest non vulnerable version

first published

latest version published

licenses detected

Direct Vulnerabilities

Fix vulnerabilities automatically