n8n-MCP: Multi-tenant MCP requests fall back to process-level n8n credentials when tenant headers are absent or
Affects n8n-mcpSource GCVE Database
Not known to be exploited · CVSS 8.1 High : upgrade to 2.51.3 soon.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.51.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 29 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade n8n-mcp to 2.51.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewn8n-mcppkg:brew/n8n-mcpOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in n8n-mcp version 2.51.3. Operators should upgrade to this version to reject malformed multi-tenant requests and prevent fallback to operator credentials. If immediate upgrade is not possible, mitigations include disabling multi-tenant mode (ENABLE_MULTI_TENANT=false), enforcing proxy-level checks to require both x-n8n-url and x-n8n-key headers on every request, and reducing the scope of the operator's API key to limit potential damage from fallback exploitation.
Description
A vulnerability in n8n-mcp's multi-tenant HTTP mode allows authenticated tenants to cause requests missing required tenant headers to fall back to the operator's own n8n instance credentials. This can lead to unauthorized access to the operator's workflows, executions, data, and credentials, and potentially remote code execution if code-node execution is permitted. The issue affects multi-tenant deployments with ENABLE_MULTI_TENANT=true and is fixed in n8n-mcp 2.51.3.
References
- github.com/czlonkowski/n8n-mcp/security/advisories/GHSA-jxx9-px88-pj69 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-45707 (opens in a new tab)
- github.com/czlonkowski/n8n-mcp/commit/853015d0897be7cf2d9d4726de195c938e4395ab (opens in a new tab)
- github.com/czlonkowski/n8n-mcp (opens in a new tab)
- github.com/czlonkowski/n8n-mcp/releases/tag/v2.51.2 (opens in a new tab)