Vulnerability in n8n-mcp (CVE-2026-42282)
Summary
Vulnerability in n8n-mcp (CVE-2026-42282). Risk of unauthorized operations or information disclosure. Exploitable via n8n_manage_credentials.data. Mitigation: upgrade to 2.47.13 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 version 2.47.13, when n8n-mcp runs in HTTP transport mode, authenticated MCP tools/call requests had their full arguments and JSON-RPC params written to server logs by the request dispatcher and several sibling code paths before any redaction. When a tool call carries credential material — most notably n8n_manage_credentials.data — the raw values can be persisted in logs. In deployments where logs are collected, forwarded to external systems, or viewable outside the request trust boundary (shared log storage, SIEM pipelines, support/ops access), this can result in disclosure of: bearer tokens and OAuth credentials sent through n8n_manage_credentials, per-tenant API keys and webhook auth headers embedded in tool arguments, arbitrary secret-bearing payloads passed to any MCP tool. The issue requires authentication (AUTH_TOKEN accepted by the server), so unauthenticated callers cannot trigger it; the runtime exposure is also reduced by an existing console-silencing layer in HTTP mode, but that layer is fragile and the values are still constructed and passed into the logger. This issue has been patched in version 2.47.13.
Source: NIST National Vulnerability Database 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-42282 has been found in n8n-mcp.
Attackers can target a specific entry point like n8n_manage_credentials.data over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade n8n-mcp to 2.47.13 or later.
If unsure, ask your IT team or search "n8n-mcp CVE-2026-42282" on the vendor's site.
CVE-2026-42282 (n8n-mcp) — CWE-532 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: n8n_manage_credentials.data / n8n_manage_credentials / AUTH_TOKEN / summarizeToolCallArgs
Patched: 2.47.13 — 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-532) exists in n8n-mcp. Attackers reach the vulnerable code path via n8n_manage_credentials.data.
Check the vendor advisory for the affected versions of n8n-mcp. Attack surface: n8n_manage_credentials.data / n8n_manage_credentials / AUTH_TOKEN / summarizeToolCallArgs.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.47.13.
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.47.13ステージング環境で 2.47.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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