Vulnerability in n8n (CVE-2026-44790)
Summary
Vulnerability in n8n (CVE-2026-44790). Successful exploitation can lead to full system takeover. Exploitable via NODES_EXCLUDE. Mitigation: upgrade to 2.20.7 or later.
Original description
The description as published by the source.
Impact
An authenticated user with permission to create or modify workflows could inject CLI flags on the Git node's Push operation allowing an attacker to read arbitrary files from the n8n server potentially leading to full compromise.
Patches
The issue has been fixed in n8n versions 1.123.43, 2.20.7, and 2.22.1. Users should upgrade to one of these versions or later to remediate the vulnerability.
Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Limit workflow creation and editing permissions to fully trusted users only.
- Disable the Git node by adding
n8n-nodes-base.gitto theNODES_EXCLUDEenvironment variable.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backwards compatibility.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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-44790 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: 8.8/10.
What to do: upgrade n8n to 2.20.7 or later.
If unsure, ask your IT team or search "n8n CVE-2026-44790" on the vendor's site.
CVE-2026-44790 (n8n) — CWE-88 / CVSS v3 8.8
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.
A vulnerability (CWE-88) exists in n8n. Attackers reach the vulnerable code path via NODES_EXCLUDE.
Check the vendor advisory for the affected versions of n8n. Attack surface: NODES_EXCLUDE.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 2.20.7.
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' . 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' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
n8nを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade n8n to 2.20.7ステージング環境で 2.20.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com