Vulnerability in n8n (CVE-2026-86994)
Summary
Vulnerability in n8n (CVE-2026-86994). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.37.7 or later.
Original description
The description as published by the source.
Impact
The endpoint /rest/active-workflows returned every active workflow ID on the instance to any member, regardless of sharing, and workflow activation, deactivation and publication push events were broadcast to every connected client, carrying workflow IDs, version IDs and activation-error detail across users. The patch scopes both the listing and the push events through the sharing service, so a user only sees workflows they can access.
Patches
The issue has been fixed in n8n versions 1.123.76, 2.37.7, and 2.38.2. 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:
- Restrict n8n instance access to fully trusted users only.
- Avoid provisioning
global:memberaccounts for untrusted users until the instance is patched.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Source: NIST National Vulnerability Database 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-86994 has been found in n8n.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade n8n to 2.37.7 or later.
If unsure, ask your IT team or search "n8n CVE-2026-86994" on the vendor's site.
CVE-2026-86994 (n8n) — CWE-862 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.37.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-862) exists in n8n.
Check the vendor advisory for the affected versions of n8n.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.37.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.37.7ステージング環境で 2.37.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com