Vulnerability in n8n-mcp (CVE-2026-54052)
Summary
Vulnerability in n8n-mcp (CVE-2026-54052). Confidential information can be exposed externally. Exploitable via Authorization header. Mitigation: upgrade to 2.56.1 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.56.1, in HTTP mode with multi-tenancy enabled through ENABLE_MULTI_TENANT=true, n8n-mcp's local workflow version history backups were not isolated per tenant, allowing an authenticated tenant to read workflow version snapshots belonging to other tenants and delete or destroy other tenants' stored backups, including full node definitions, credential references, and authorization headers. This issue is fixed in version 2.56.1.
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-54052 has been found in n8n-mcp.
Attackers can target a specific entry point like Authorization header over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.9/10.
What to do: upgrade n8n-mcp to 2.56.1 or later.
If unsure, ask your IT team or search "n8n-mcp CVE-2026-54052" on the vendor's site.
CVE-2026-54052 (n8n-mcp) — CWE-639 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: Authorization header
Patched: 2.56.1 — 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-639) exists in n8n-mcp. Attackers reach the vulnerable code path via Authorization header.
Check the vendor advisory for the affected versions of n8n-mcp. Attack surface: Authorization header.
Severity: Critical (CVSS 9.9/10). Confidential information can be exposed externally.
Update to 2.56.1.
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.56.1ステージング環境で 2.56.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com