Vulnerability in n8n (CVE-2026-65014)
Summary
Vulnerability in n8n (CVE-2026-65014). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.27.4 or later.
Original description
The description as published by the source.
Impact
The DELETE /${restEndpoint}/test-webhook/:id route is registered before the authentication middleware is applied, allowing any unauthenticated network caller who knows a workflow ID to cancel that workflow's active test webhook registration.
The impact is limited to disrupting in-progress test sessions. Production webhooks, persistent workflow state, and stored data are not affected.
Patches
Users should upgrade to the patched version once available to remediate the vulnerability.
Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Restrict network access to the n8n instance to fully trusted users only.
- Place the n8n instance behind a reverse proxy or firewall that requires authentication before reaching the REST API.
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-65014 has been found in n8n.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade n8n to 2.27.4 or later.
If unsure, ask your IT team or search "n8n CVE-2026-65014" on the vendor's site.
CVE-2026-65014 (n8n) — CWE-306 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.27.4 — 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-306) exists in n8n.
Check the vendor advisory for the affected versions of n8n.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.27.4.
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.27.4ステージング環境で 2.27.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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 vulncheck.com
- web github.com
- web github.com
- web github.com
- web github.com