Authorization Flaw in n8n (CVE-2026-65015)
Summary
Vulnerability in n8n (CVE-2026-65015). Successful exploitation can lead to full system takeover. Exploitable via agents. Mitigation: upgrade to 2.29.8 or later.
Original description
The description as published by the source.
n8n versions before 2.30.1 contain a privilege escalation vulnerability in the AI Agents feature where the node-execution tool lacks proper authorization checks. A Project Viewer user can escalate privileges by chatting with an agent that has node tools enabled, executing arbitrary nodes and accessing credential secrets without proper authorization verification.
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-65015 has been found in n8n.
Attackers can target a specific entry point like agents 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.29.8 or later.
If unsure, ask your IT team or search "n8n CVE-2026-65015" on the vendor's site.
CVE-2026-65015 (n8n) — CWE-863 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: agents / N8N_ENABLED_MODULES
Patched: 2.29.8 — 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.
Incorrect authorization (CWE-863) exists in n8n. Attackers reach the vulnerable code path via agents.
Check the vendor advisory for the affected versions of n8n. Attack surface: agents / N8N_ENABLED_MODULES.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 2.29.8.
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.29.8ステージング環境で 2.29.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory vulncheck.com
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com