Skip to main content
← npm

n8n-mcp

9 known vulnerabilities (1 critical, 4 high, 4 medium), with the versions each affects and the releases that fix them.

Latest release
Not known: cve.now hasn't read this package's releases
Newest unaffected release
Not known without release data
Advisories
9 · 1 critical, 4 high, 4 medium
Weekly downloads
83.2K
Dependents
0
Registry
npm

Advisories 9

  • CVE-2026-55608Medium 4.2

    n8n-MCP: Incorrect authorization can expose default-scope workflow version backups in multi-tenant HTTP mode

    Affected: fixed in 2.57.4.

  • CVE-2026-54052Critical 9.9

    n8n-MCP: Cross-tenant access to workflow version backups in multi-tenant HTTP deployments

    Affected: fixed in 2.56.1.

  • CVE-2026-45582Medium 6.5

    n8n-MCP: Workflow telemetry sanitizer could retain partial values from URL-shaped node parameters

    Affected: fixed in 2.51.3.

  • n8n-MCP: Multi-tenant MCP requests fall back to process-level n8n credentials when tenant headers are absent or incomplete

    Affected: fixed in 2.51.2.

  • n8n-MCP: Authenticated SSRF in n8n-mcp webhook and API client paths

    Affected: from 2.18.7, fixed in 2.50.2.

  • CVE-2026-42282Medium 4.3

    n8n-MCP: Sensitive MCP tool-call arguments logged on authenticated requests in HTTP mode

    Affected: fixed in 2.47.13.

  • CVE-2026-41495Medium 5.3

    n8n-MCP Logs Sensitive Request Data on Unauthorized /mcp Requests

    Affected: fixed in 2.47.11.

  • n8n-MCP: IPv4-mapped IPv6 addresses bypass SSRF protection in validateUrlSync(), enabling full SSRF for SDK embedders

    Affected: from 2.47.4, fixed in 2.47.14.

  • n8n-MCP has an Authenticated SSRF via instance-URL header in multi-tenant HTTP mode

    Affected: fixed in 2.47.4.