Vulnerability in n8n (CVE-2026-56360)
Summary
Vulnerability in n8n (CVE-2026-56360). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.6.2 or later.
Original description
The description as published by the source.
Impact
An attacker who knows the webhook URL of a workflow using the ZendeskTrigger node could send unsigned POST requests and trigger the workflow with arbitrary data. The node does not verify the HMAC-SHA256 signature that Zendesk attaches to every outbound webhook, allowing any party to inject crafted payloads into the connected workflow.
Patches
The issue has been fixed in n8n versions 2.6.2 and 1.123.18. 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.
- Restrict network access to the n8n webhook endpoint to known Zendesk IP ranges.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
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-56360 has been found in n8n.
Risk of unauthorized operations or information disclosure. CVSS score: 4.0/10.
What to do: upgrade n8n to 2.6.2 or later.
If unsure, ask your IT team or search "n8n CVE-2026-56360" on the vendor's site.
CVE-2026-56360 (n8n) — CWE-290 / CVSS v3 4.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.6.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.
A vulnerability (CWE-290) exists in n8n.
Check the vendor advisory for the affected versions of n8n.
Severity: Medium (CVSS 4.0/10). Risk of unauthorized operations or information disclosure.
Update to 2.6.2.
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.6.2ステージング環境で 2.6.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory disclosure@vulncheck.com
- package github.com
- web github.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com