CVE-2026-45707
n8n-MCP is an MCP server that provides AI assistants access to n8n …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/czlonkowski/n8n-mcp/security/advisories/GHSA-jxx9-px88-pj69
- github.com/czlonkowski/n8n-mcp/commit/853015d0897be7cf2d9d4726de195c938e4395ab
- github.com/czlonkowski/n8n-mcp/releases/tag/v2.51.2
- github.com/advisories/GHSA-jxx9-px88-pj69
- nvd.nist.gov/vuln/detail/CVE-2026-45707
- nvd.nist.gov/vuln/detail/CVE-2026-45707
- cve.org/CVERecord?id=CVE-2026-45707
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.