CVE-2026-45707— n8n-MCP 访问控制错误漏洞

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

n8n-MCP is an MCP server that provides AI assistants access to n8n node documentation, properties, and operations. Prior to 2.51.2, when ENABLE_MULTI_TENANT=true, the HTTP transport documents that the target n8n instance is selected per-request from x-n8n-url / x-n8n-key headers. Requests that omitted those headers — or supplied only one of them — silently fell back to the process-level N8N_API_URL / N8N_API_KEY credentials configured for the operator's own n8n instance. As a result, an authenticated MCP tenant could cause n8n management calls to execute against the operator's instance instead of its own. This affects HTTP-mode deployments of n8n-mcp that are run as a shared multi-tenant service. Single-tenant deployments (ENABLE_MULTI_TENANT unset or false) are not affected. This vulnerability is fixed in 2.51.2.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

访问控制不恰当

n8n-MCP 访问控制错误漏洞

n8n-MCP是Romuald Członkowski个人开发者的一个连接AI助手与自动化工作流平台的模型上下文协议服务器。 n8n-MCP 2.51.2之前版本存在访问控制错误漏洞，该漏洞源于启用多租户时，HTTP传输中省略或仅提供部分标头时静默回退到进程级凭据，可能导致经过身份验证的MCP租户对操作员实例执行n8n管理调用。

N/A

N/A