← Back
CVE-2026-44789
critical
CVSS 9.9
Vulnerability in n8n (CVE-2026-44789)
Summary
vulnerability in n8n (CVE-2026-44789). Successful exploitation can lead to full system takeover. Exploitable via ``NODES_EXCLUDE``. Mitigation: upgrade to `2.20.7` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44789** has been found in n8n.
Attackers can target a specific entry point like ``NODES_EXCLUDE`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade n8n to **2.20.7** or later.
If unsure, ask your IT team or search "n8n CVE-2026-44789" on the vendor's site.
CVE-2026-44789 (n8n) — CWE-1321 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `NODES_EXCLUDE`
Patched: `2.20.7` — 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-1321) exists in n8n. Attackers reach the vulnerable code path via ``NODES_EXCLUDE`` without authentication.
📍 Affected scope
n8n — . Attack surface: `NODES_EXCLUDE`.
🔥 Severity
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.20.7**.
🛡️ 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' .` 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' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `n8n` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade n8n to 2.20.7ステージング環境で 2.20.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
n8n
[{"type":"SEMVER","events":[{"introduced":"2.0.0-rc.0"},{"fixed":"2.20.7"}]}]