Vulnerability in n8n (CVE-2026-86075)
Summary
Vulnerability in n8n (CVE-2026-86075). Risk of unauthorized operations or information disclosure. Exploitable via redirect_uris. Mitigation: upgrade to 2.37.7 or later.
Original description
The description as published by the source.
Impact
The OAuth Dynamic Client Registration endpoints validated field sizes only for redirect_uris, leaving client_name and grant_types bounded by presence checks alone. An unauthenticated remote caller could submit arbitrarily large values in either field and have them persisted to the database. Repeated registration therefore grew persistent storage without limit and without any account on the instance. The patch caps client_name at its column length and limits grant_types to the grant types the server actually implements, with the array capped at that count.
Patches
The issue has been fixed in n8n versions 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 network access to the n8n instance so that only trusted clients can reach it.
- Place the instance behind a reverse proxy configured to enforce strict request body size limits below the default 16 MiB.
- Monitor database size for unexpected growth and audit the
oauth_clientstable for anomalous entries.
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-86075 has been found in n8n.
Attackers can target a specific entry point like redirect_uris over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade n8n to 2.37.7 or later.
If unsure, ask your IT team or search "n8n CVE-2026-86075" on the vendor's site.
CVE-2026-86075 (n8n) — CWE-770 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: redirect_uris / client_name / grant_types / oauth_clients
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-770) exists in n8n. Attackers reach the vulnerable code path via redirect_uris without authentication.
Check the vendor advisory for the affected versions of n8n. Attack surface: redirect_uris / client_name / grant_types / oauth_clients.
Severity: High (CVSS 7.5/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 nvd.nist.gov
- web github.com