Homepage

n8n-mcp@2.48.1

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

  • latest version

    2.66.0

  • latest non vulnerable version

    2.66.0

  • first published

    1 years ago

  • latest version published

    12 hours ago

  • licenses detected

  • View n8n-mcp package health on Snyk  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    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
    VulnerabilityVulnerable Version
    • M
    Incorrect Authorization

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

    Affected versions of this package are vulnerable to Incorrect Authorization in the workflow_versions. An attacker can access or delete sensitive workflow-version backups by sending crafted requests in multi-tenant HTTP mode.

    Note: This is only exploitable if the application is running with ENABLE_MULTI_TENANT=true and default-scope backups from a prior single-tenant deployment are present.

    How to fix Incorrect Authorization?

    Upgrade n8n-mcp to version 2.57.4 or higher.

    <2.57.4
    • M
    Missing Authorization

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

    Affected versions of this package are vulnerable to Missing Authorization in the workflow version history process in multi-tenant HTTP deployments due to improper isolation of stored backups between tenants. An attacker can access and manipulate other tenants' workflow version snapshots, potentially exposing sensitive data such as credential references and authorization headers, by making authenticated requests as a different tenant.

    Note: This is only exploitable if the deployment is configured in HTTP mode with multi-tenancy enabled (ENABLE_MULTI_TENANT=true).

    How to fix Missing Authorization?

    Upgrade n8n-mcp to version 2.56.1 or higher.

    <2.56.1
    • H
    Failing Open

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

    Affected versions of this package are vulnerable to Failing Open when handing multi-tenant HTTP requests (ENABLE_MULTI_TENANT=true) containing one or neither of the x-n8n-url and x-n8n-key headers. An operator can gain unauthorized access to workflows, executions, data-table contents, and credential metadata, and potentially escalate privileges to execute arbitrary code within the operator's environment because the absence of these headers falls back to associating the request with process-level credentials. This is only exploitable if the deployment is running in HTTP mode.

    How to fix Failing Open?

    Upgrade n8n-mcp to version 2.51.2 or higher.

    <2.51.2
    • M
    Insertion of Sensitive Information Into Sent Data

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

    Affected versions of this package are vulnerable to Insertion of Sensitive Information Into Sent Data in the telemetry sanitization process in event-validator.ts. An operator with access to the telemetry backend can access fragments of URL parameters, exposing confidential information such as customer or tenant identifiers, short secrets in query strings, or signed request parameters. Workflow execution data and credentials are not exposed.

    How to fix Insertion of Sensitive Information Into Sent Data?

    Upgrade n8n-mcp to version 2.51.3 or higher.

    <2.51.3
    • 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) 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.

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

    Upgrade n8n-mcp to version 2.50.2 or higher.

    >=2.18.7 <2.50.2
    • 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 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.

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

    Upgrade n8n-mcp to version 2.50.1 or higher.

    <2.50.1
    Go back to all versions of this package