Cross-Site Scripting (XSS) in n8n (CVE-2026-54302)
Summary
Cross-site scripting in n8n (CVE-2026-54302). Confidential information can be exposed externally. Exploitable via webhookId. Mitigation: upgrade to 2.25.7 or later.
Original description
The description as published by the source.
n8n is an open source workflow automation platform. Prior to 1.123.55, 2.25.7, and 2.26.2, an authenticated user with workflow edit access could inject arbitrary JavaScript into the Chat Trigger's generated page by setting a malicious webhookId. When a logged-in user visited the chat URL, the injected code executed in the n8n origin with that user's session privileges. This vulnerability is fixed in 1.123.55, 2.25.7, and 2.26.2.
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-54302 has been found in n8n.
Attackers can target a specific entry point like webhookId over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.4/10.
What to do: upgrade n8n to 2.25.7 or later.
If unsure, ask your IT team or search "n8n CVE-2026-54302" on the vendor's site.
CVE-2026-54302 (n8n) — CWE-79 / CVSS v3 5.4
Attack vector: remote (network-reachable)
Attack surface: webhookId / NODES_EXCLUDE
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.
Cross-site scripting (XSS) (CWE-79) exists in n8n. Attackers reach the vulnerable code path via webhookId.
Check the vendor advisory for the affected versions of n8n. Attack surface: webhookId / NODES_EXCLUDE.
Severity: Medium (CVSS 5.4/10). Confidential information can be exposed externally.
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 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.25.7ステージング環境で 2.25.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com