NPM · JULY 2026 · EARLY WARNING

n8n SSRF Vulnerability Under Investigation: Update Recommended

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.

GHSA-38FJ-36M5-783CGHSA-9W78-79Q7-R4FPSeverity: HIGH

An early warning has been issued regarding a potential server-side request forgery (SSRF) vulnerability in n8n versions before 1.123.64. Users of affected versions are advised to update.

What happened

Reportedly, n8n versions prior to 1.123.64 contain a vulnerability in the dynamic-node-parameters endpoints that lack proper authorization scopes. This appears to allow authenticated attackers to supply absolute URLs in routing configuration, potentially overriding baseURL restrictions and enabling the n8n server to issue HTTP requests to arbitrary internal targets when SSRF protection is disabled.

The vulnerability is currently under investigation, and it is recommended that users upgrade to n8n version 1.123.64 or later to mitigate potential risks. For more detailed information, primary sources should be consulted.

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If n8n is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats