Vulnerability in n8n-mcp (CVE-2026-45707)
Summary
Vulnerability in n8n-mcp (CVE-2026-45707). Confidential information can be exposed externally. Exploitable via N8N_API_URL. Mitigation: upgrade to 2.51.2 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45707 has been found in n8n-mcp.
Attackers can target a specific entry point like N8N_API_URL over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade n8n-mcp to 2.51.2 or later.
If unsure, ask your IT team or search "n8n-mcp CVE-2026-45707" on the vendor's site.
CVE-2026-45707 (n8n-mcp) — CWE-284 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: N8N_API_URL / N8N_API_KEY / ENABLE_MULTI_TENANT / false
Patched: 2.51.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-284) exists in n8n-mcp. Attackers reach the vulnerable code path via N8N_API_URL.
Check the vendor advisory for the affected versions of n8n-mcp. Attack surface: N8N_API_URL / N8N_API_KEY / ENABLE_MULTI_TENANT / false.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 2.51.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'n8n-mcp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'n8n-mcp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
n8n-mcpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade n8n-mcp to 2.51.2ステージング環境で 2.51.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web github.com