GHSA-vhf8-cg2h-cg3p: n8n: SSRF Protection Bypass via MCP Client Node

Summary

The MCP Client node in n8n sent requests to user-supplied endpoints without routing them through SSRF protection or pinning the resolved address. An authenticated user who could create or edit a workflow could make the server connect to internal or blocked hosts and read the responses back through the workflow. The issue affects instances with SSRF protection enabled.

Mitigation

Fixed in n8n versions 2.31.5 and 2.32.1; upgrade to one of these or later. If upgrading is not immediately possible, temporary mitigations include restricting instance access to fully trusted users only, disabling the MCP Client node by adding it to the `NODES_EXCLUDE` environment variable, and restricting network egress from the n8n host to block internal and link-local address ranges. These workarounds do not fully remediate the risk and should only be short-term measures.

Affected packages in the Exposure Registry

Matched by package name and ecosystem. Each entry shows whether the package delegates to a language model and how many tracked packages depend on it.

• n8nnpmLLM dependency since 2026-02-10

Topics

• Model Context Protocol

Related items

• MediumCVE-2026-127202: MLflow path traversal through model_id in the log outputs APISimilar attack · NVD/CVE Database
• LowAI chatbots are recommending fake retail websites, study findsSimilar attack · The Verge (AI)
• MediumPalo Alto tracks a massive Chinese AI attack that sadly lives up to industry fearsSimilar attack · CSO Online
• MediumAttackers Use Autonomous AI to Target Semiconductor, Defense and Civil Society SectorsSimilar attack · Palo Alto Unit 42
• MediumCVE-2026-126994: braindecode model config deserialization flaw via activation argumentSimilar attack · NVD/CVE Database