Homepage

n8n-mcp@2.50.5

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

  • latest version

    2.57.4

  • latest non vulnerable version

    2.57.4

  • first published

    11 months ago

  • latest version published

    17 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
    • 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
    Go back to all versions of this package