← Back
CVE-2026-44694
Vulnerability in n8n-mcp (CVE-2026-44694)
Summary
vulnerability in n8n-mcp (CVE-2026-44694). Risk of unauthorized operations or information disclosure. Exploitable via ``N8N_API_URL``. Mitigation: upgrade to `2.50.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44694** has been found in n8n-mcp.
Attackers can target a specific entry point like ``N8N_API_URL`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade n8n-mcp to **2.50.2** or later.
If unsure, ask your IT team or search "n8n-mcp CVE-2026-44694" on the vendor's site.
CVE-2026-44694 (n8n-mcp) — CWE-367 /
Attack surface: `N8N_API_URL` / `AUTH_TOKEN` / `strict` / `metadata.google.internal`
Patched: `2.50.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.
❓ What is the problem
**A vulnerability** (CWE-367) exists in n8n-mcp. Attackers reach the vulnerable code path via ``N8N_API_URL`` without authentication.
📍 Affected scope
n8n-mcp — . Attack surface: `N8N_API_URL` / `AUTH_TOKEN` / `strict` / `metadata.google.internal`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.50.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade n8n-mcp to 2.50.2ステージング環境で 2.50.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
n8n-mcp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.50.2"}]}]