Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-65593 medium CVSS 5.4

SSRF (Server-Side Request Forgery) in n8n (CVE-2026-65593)

Summary

SSRF in n8n (CVE-2026-65593). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.29.8 or later.

Original description

The description as published by the source.

Impact

Endpoints in /rest/dynamic-node-parameters/ lacked authorization scopes, making it reachable by any authenticated user with no workflow creation or execution required.

By supplying an absolute URL in the routing configuration, a caller could override the node type's declared baseURL, defeating the restriction meant to confine requests to the node's own upstream service. With SSRF protection disabled by default (N8N_SSRF_PROTECTION_ENABLED=false), this let an authenticated user make the n8n server issue HTTP requests to arbitrary internal targets.

Patches

The issue has been fixed in n8n versions 1.123.64, 2.29.8, and 2.30.1. Users should upgrade to this version 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.
  • Set N8N_SSRF_PROTECTION_ENABLED=true to enable SSRF filtering for private IP ranges and cloud metadata endpoints.
  • Restrict network egress from the n8n host to limit reachable internal services.

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-65593 has been found in n8n.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade n8n to 2.29.8 or later.
If unsure, ask your IT team or search "n8n CVE-2026-65593" on the vendor's site.

CVE-2026-65593 (n8n) — CWE-918 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.29.8 — apply immediately
Workaround: set N8N_SSRF_PROTECTION_: ENABLED
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

SSRF (CWE-918) exists in n8n.

📍 Affected scope

Check the vendor advisory for the affected versions of n8n.

🔥 Severity

Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.29.8.

🛡️ Workaround

Workaround: set N8N_SSRF_PROTECTION_: ENABLED

🔍 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 temporary workaround mitigate 
    set N8N_SSRF_PROTECTION_: ENABLED

    パッチが適用されるまでの応急処置として、set N8N_SSRF_PROTECTION_: ENABLED を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade n8n to 2.29.8

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

  4. 4
    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