Vulnerability in n8n (CVE-2026-56776)
Summary
Vulnerability in n8n (CVE-2026-56776). Risk of unauthorized operations or information disclosure. Exploitable via POST /workflows/{workflowId}/test-runs/new. Mitigation: upgrade to 2.25.7 or later.
Original description
The description as published by the source.
n8n before 1.123.55, 2.25.7, and 2.26.2 contains an authorization bypass in the POST /workflows/{workflowId}/test-runs/new endpoint, which authorizes access using the workflow:read scope instead of workflow:execute. An authenticated user with read-only access to a workflow can trigger a real evaluation test run, causing the workflow to execute via the internal workflow runner and resulting in unintended outbound API calls, data mutations, or other side effects in connected downstream systems. The issue primarily affects instances using the Evaluations feature where RBAC project roles grant workflow:read without workflow:execute.
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-56776 has been found in n8n.
Attackers can target a specific entry point like POST /workflows/{workflowId}/test-runs/new over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.4/10.
What to do: upgrade n8n to 2.25.7 or later.
If unsure, ask your IT team or search "n8n CVE-2026-56776" on the vendor's site.
CVE-2026-56776 (n8n) — CWE-284 / CVSS v3 7.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /workflows/{workflowId}/test-runs/new
Patched: 2.25.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-284) exists in n8n. Attackers reach the vulnerable code path via POST /workflows/{workflowId}/test-runs/new.
Check the vendor advisory for the affected versions of n8n. Attack surface: POST /workflows/{workflowId}/test-runs/new.
Severity: High (CVSS 7.4/10). Risk of unauthorized operations or information disclosure.
Update to 2.25.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 POST /workflows/{workflowId}/test-runs/new requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /workflows/{workflowId}/test-runs/new' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /workflows/{workflowId}/test-runs/newへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade n8n to 2.25.7ステージング環境で 2.25.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /workflows/{workflowId}/test-runs/new on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory vulncheck.com
- advisory github.com
- package github.com
- web github.com