Homepage

n8n-mcp@2.13.0

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

  • latest version

    2.73.0

  • latest non vulnerable version

    2.73.0

  • first published

    1 years ago

  • latest version published

    8 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) 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
    • M
    Insertion of Sensitive Information into Log File

    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 Log File via the request dispatcher and related logging. An attacker can obtain sensitive information, such as credentials or API keys, by accessing improperly redacted server logs.

    Note: This is only exploitable if the application is running in HTTP transport mode and logs are accessible outside the trusted boundary.

    How to fix Insertion of Sensitive Information into Log File?

    Upgrade n8n-mcp to version 2.47.13 or higher.

    <2.47.13
    • M
    Insertion of Sensitive Information into Log File

    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 Log File in the POST /mcp endpoint. An attacker can cause sensitive information such as bearer tokens, API keys, and request payloads to be written to server logs by sending unauthorized requests.

    Note: This is only exploitable if the application is running in HTTP transport mode and logs are accessible outside the trusted boundary.

    How to fix Insertion of Sensitive Information into Log File?

    Upgrade n8n-mcp to version 2.47.11 or higher.

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