Vulnerability  ·  2026-11-16

n8n-mcp cross-tenant authorization bypass exposes workflow snapshots, credential references and auth headers (CVE-2026-54052)

VulnerabilityHigh impactGlobalCVE-2026-54052
n8n-mcp is an MCP server that lets AI assistants operate n8n. Prior to 2.56.1, in HTTP mode with multi-tenancy enabled, workflow version-history backups were not isolated per tenant (CWE-639/CWE-862). An authenticated tenant could read workflow snapshots belonging to other tenants and delete or destroy other tenants' stored backups, including complete node definitions, credential references and authorization headers. CVSS 3.1 base score 9.9 (Critical), scope changed. Fixed in 2.56.1.
n8n is widely used for AI workflow automation, and n8n-mcp hands an AI assistant read/write access to those workflows and their credentials. Cross-tenant leakage of stored authorization headers and credential references lets one tenant harvest secrets used by other tenants' automation, potentially granting access to downstream systems the MCP server can reach.
An authenticated tenant sends crafted MCP requests in a multi-tenant HTTP deployment; because local workflow-version backups were not isolated per tenant, the tenant can read and delete other tenants' snapshots — including full node definitions, credential references and authorization headers.
n8n-mcp < 2.56.1 (HTTP mode, ENABLE_MULTI_TENANT=true)
Upgrade n8n-mcp to 2.56.1 or newer (GitHub GHSA-j6r7-6fhx-77wx). Disable ENABLE_MULTI_TENANT if multi-tenancy is not required.
GHSA-j6r7-6fhx-77wx (n8n-mcp vendor advisory)n8n-mcp v2.56.1 release notesCheck Point CPAI-2026-17496 (CVE-2026-54052)
See this in the live feed Explore related AI security and governance findings — updated every morning.
Open the feed →