Summary
n8n: SSRF Protection Bypass via MCP Client Node
Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Restrict n8n instance access to fully trusted users only.
- Disable the MCP Client node by adding it to the
NODES_EXCLUDEenvironment variable. - Restrict network egress from the n8n host to block access to internal and link-local address ranges at the network level.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Impact
On an n8n instance with SSRF protection enabled, the MCP Client node sent requests to a user-supplied endpoint without routing them through that protection and without pinning the resolved address. An authenticated user who could create or edit a workflow could therefore cause the server to connect to internal or otherwise blocked hosts and read the responses back through the workflow, exposing internal services the SSRF protection was meant to protect.
Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The issue has been fixed in n8n versions 2.31.5 and 2.32.1. Users should upgrade to one of these versions or later to remediate the vulnerability.
Frequently Asked Questions
- What is GHSA-VHF8-CG2H-CG3P? GHSA-VHF8-CG2H-CG3P is a medium-severity server-side request forgery (SSRF) vulnerability in n8n (npm), affecting versions >= 2.32.0, < 2.32.1. It is fixed in 2.32.1, 2.31.5. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
- Which versions of n8n are affected by GHSA-VHF8-CG2H-CG3P? n8n (npm) versions >= 2.32.0, < 2.32.1 is affected.
- Is there a fix for GHSA-VHF8-CG2H-CG3P? Yes. GHSA-VHF8-CG2H-CG3P is fixed in 2.32.1, 2.31.5. Upgrade to this version or later.
- Is GHSA-VHF8-CG2H-CG3P exploitable, and should I be worried? Whether GHSA-VHF8-CG2H-CG3P is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-VHF8-CG2H-CG3P is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-VHF8-CG2H-CG3P?
- Upgrade
n8nto 2.32.1 or later - Upgrade
n8nto 2.31.5 or later
- Upgrade