GHSA-vhf8-cg2h-cg3p: n8n SSRF Protection Bypass Vulnerability

MODERATE
CWE-918
Published
Advisory Summary

GHSA-vhf8-cg2h-cg3p is a MODERATE ssrf protection bypass vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting n8n libraries in the npm ecosystem. The issue involves ssrf protection bypass via mcp client node. Remediation is available by upgrading affected packages to version 2.32.1, 2.31.5.

GHSA-vhf8-cg2h-cg3p at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-vhf8-cg2h-cg3p
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product n8n
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-vhf8-cg2h-cg3p

To remediate this vulnerability, upgrade all affected n8n dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

n8n fixed: 2.32.1
npm install n8n@2.32.1
n8n fixed: 2.31.5
npm install n8n@2.31.5
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls n8n

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-vhf8-cg2h-cg3p, inspect your project dependencies using npm:

npm ls n8n

Analyze the terminal output to locate any version of n8n in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.32.1), your application is affected.

Note: The npm ls n8n command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In n8n, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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. ## Patches 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. ## 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_EXCLUDE` environment 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.

GHSA-vhf8-cg2h-cg3p Affected n8n Versions

2 component(s)
Fixed Versions:
2.32.12.31.5
Product / Package Ecosystem Affected Versions Fixed Version
n8n
npm
≥ 2.32.0
< 2.32.1
2.32.1
n8n
npm
< 2.31.5
2.31.5

References

Frequently Asked Questions

What is GHSA-vhf8-cg2h-cg3p?
GHSA-vhf8-cg2h-cg3p is a security vulnerability in n8n involving SSRF Protection Bypass via MCP Client Node under CWE-918: Server-Side Request Forgery (SSRF).
Which n8n versions are affected?
Affected versions include releases prior to 2.32.1, 2.31.5 across affected packages: n8n.
What version fixes GHSA-vhf8-cg2h-cg3p?
Upgrading to 2.32.1, 2.31.5 (or the latest patched release for your respective branch) resolves the vulnerability.
Is n8n affected?
Yes, n8n is affected in releases prior to 2.32.1, 2.31.5. Upgrade your dependency to 2.32.1, 2.31.5 or later.
What CWE is associated with GHSA-vhf8-cg2h-cg3p?
GHSA-vhf8-cg2h-cg3p is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check npm dependencies for GHSA-vhf8-cg2h-cg3p?
Run the dependency tree command: 'npm ls n8n'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-vhf8-cg2h-cg3p",
  "modified" : "2026-07-22T22:07:04Z",
  "published" : "2026-07-22T22:07:04Z",
  "aliases" : [ ],
  "summary" : "n8n: SSRF Protection Bypass via MCP Client Node",
  "details" : "## Impact\n\nOn 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.\n\n## Patches\n\nThe 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.\n\n## Workarounds\n\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Restrict n8n instance access to fully trusted users only.\n- Disable the MCP Client node by adding it to the `NODES_EXCLUDE` environment variable.\n- Restrict network egress from the n8n host to block access to internal and link-local address ranges at the network level.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.32.0"
      }, {
        "fixed" : "2.32.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.31.5"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/security/advisories/GHSA-vhf8-cg2h-cg3p"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/commit/f69dfc6dd2178a14ea1624d2e1d403c2e755042f"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/n8n-io/n8n"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.31.5"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.32.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-22T22:07:04Z",
    "nvd_published_at" : null
  }
}