Categories
CVE-2026-65016 high CVSS 8.8

Vulnerability in n8n (CVE-2026-65016)

Summary

Vulnerability in n8n (CVE-2026-65016). Successful exploitation can lead to full system takeover. Exploitable via N8N_SSO_SCOPES_PROVISION_INSTANCE_ROLE. Mitigation: upgrade to 2.29.8 or later.

Original description

The description as published by the source.

n8n versions before 1.123.64, 2.29.8, and 2.30.1 contain a privilege escalation vulnerability in Enterprise SSO instance-role provisioning. The provisioning path maps an IdP-asserted role claim to an n8n global role but does not prevent assignment of the global:owner role (unlike the token-exchange identity path, which rejects it). An SSO-authenticated user whose instance-role claim resolves to global:owner is provisioned as instance owner, gaining full administrative control over workflows, credentials, users, and instance configuration. Exploitation requires that Enterprise SSO is configured, instance-role provisioning is enabled via N8N_SSO_SCOPES_PROVISION_INSTANCE_ROLE (disabled by default), and the attacker controls the instance-role claim value issued by the IdP.

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-65016 has been found in n8n.
Attackers can target a specific entry point like N8N_SSO_SCOPES_PROVISION_INSTANCE_ROLE over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade n8n to 2.29.8 or later.
If unsure, ask your IT team or search "n8n CVE-2026-65016" on the vendor's site.

CVE-2026-65016 (n8n) — CWE-639 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: N8N_SSO_SCOPES_PROVISION_INSTANCE_ROLE
Patched: 2.29.8 — 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.

❓ What is the problem

A vulnerability (CWE-639) exists in n8n. Attackers reach the vulnerable code path via N8N_SSO_SCOPES_PROVISION_INSTANCE_ROLE.

📍 Affected scope

Check the vendor advisory for the affected versions of n8n. Attack surface: N8N_SSO_SCOPES_PROVISION_INSTANCE_ROLE.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2.29.8.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify exposure identify
    grep -r 'n8n' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で n8n を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade n8n to 2.29.8

    ステージング環境で 2.29.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm n8n
[{"type":"SEMVER","events":[{"introduced":"2.0.0-rc.0"},{"fixed":"2.29.8"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details