GHSA-8g7g-hmwm-6rv2: N8n mcp Path Traversal Vulnerability

HIGH
Share
CVSS 8.3
CWE-918 CWE-200 CWE-22
Published
Advisory Summary

GHSA-8g7g-hmwm-6rv2 is a HIGH (CVSS 8.3) path traversal vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting N8n mcp libraries in the npm ecosystem. The issue involves n8n-mcp affected by path traversal, redirect-following ssrf, and telemetry payload exposure. Remediation is available by upgrading affected packages to version 2.50.1.

GHSA-8g7g-hmwm-6rv2 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-8g7g-hmwm-6rv2
Severity HIGH
CVSS v3.1 Base Score 8.3
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product N8n mcp
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 8.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability Low (A:L)

How to Fix GHSA-8g7g-hmwm-6rv2

To remediate this vulnerability, upgrade all affected N8n mcp 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-mcp fixed: 2.50.1 
npm install n8n-mcp@2.50.1
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-mcp

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-8g7g-hmwm-6rv2, inspect your project dependencies using npm:

npm ls n8n-mcp

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

Note: The npm ls n8n-mcp 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 mcp, 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 `n8n-mcp` versions before 2.50.1 contained three independently-reported issues affecting deployments that run the n8n API integration: 1. **Caller-supplied identifiers were not validated before being used as URL path segments** by the n8n API client. An authenticated MCP caller passing a crafted workflow id could cause outbound requests carrying the configured n8n API key to land on other same-origin endpoints, bypassing handler-level access controls (including `DISABLED_TOOLS`). 2. **Validated webhook, form, and chat trigger URLs followed redirects.** A URL that passed initial validation could redirect the outbound request to a host that would otherwise have been rejected, with the response body returned to the caller. Reachable as non-blind SSRF over authenticated MCP calls. 3. **Mutation telemetry stored unredacted operation payloads.** On instances running with the default opt-in telemetry, partial-update operation diffs were uploaded without redaction. Operation values can carry the same node-parameter values the workflow contains, including bearer tokens, API keys, and webhook secrets. ## Severity CVSS 8.3 (HIGH). Exploitation requires an authenticated MCP caller and an n8n API integration configured with an n8n API key. ## Patched versions Upgrade to `n8n-mcp >= 2.50.1`. ## Workarounds - For issues (1) and (2): restrict network access to the HTTP transport (firewall, reverse-proxy ACL, or VPN) so only trusted callers can reach the MCP HTTP port; or switch to stdio mode, which exposes no HTTP surface for these issues. - For issue (3): set `N8N_MCP_TELEMETRY_DISABLED=true` in the environment before starting the server, or run `npx n8n-mcp telemetry disable` once. ## Credit Reported by @cybercraftsolutionsllc.

GHSA-8g7g-hmwm-6rv2 Affected N8n mcp Versions

1 component(s)
Fixed Versions:
2.50.1
Product / Package Ecosystem Affected Versions Fixed Version
n8n-mcp
npm/n8n-mcp
npm
< 2.50.1
2.50.1

References

GitHub Advisory / Wiki ADVISORY
https://github.com/czlonkowski/n8n-mcp/security/advisories/GHSA-8g7g-hmwm-6rv2
Security Fix Commit FIX COMMIT
https://github.com/czlonkowski/n8n-mcp/commit/1cfe9c6bddb4b1634e6e23323c18ea35fd196999
N8n mcp Source Repository REPOSITORY
https://github.com/czlonkowski/n8n-mcp
N8n mcp Release RELEASE
https://github.com/czlonkowski/n8n-mcp/releases/tag/v2.50.1

Frequently Asked Questions

What is GHSA-8g7g-hmwm-6rv2?
GHSA-8g7g-hmwm-6rv2 is a security vulnerability in N8n mcp involving n8n-mcp affected by path traversal, redirect-following SSRF, and telemetry payload exposure under CWE-918: Server-Side Request Forgery (SSRF).
Which N8n mcp versions are affected?
Affected versions include releases prior to 2.50.1 across affected packages: n8n-mcp.
What version fixes GHSA-8g7g-hmwm-6rv2?
Upgrading to 2.50.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is n8n-mcp affected?
Yes, n8n-mcp is affected in releases prior to 2.50.1. Upgrade your dependency to 2.50.1 or later.
What is the CVSS score of GHSA-8g7g-hmwm-6rv2?
GHSA-8g7g-hmwm-6rv2 has a CVSS v3.1 base score of 8.3 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L.
What CWE is associated with GHSA-8g7g-hmwm-6rv2?
GHSA-8g7g-hmwm-6rv2 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-8g7g-hmwm-6rv2?
Run the dependency tree command: 'npm ls n8n-mcp'. 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
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-8g7g-hmwm-6rv2",
  "modified" : "2026-05-08T17:00:09Z",
  "published" : "2026-05-08T17:00:09Z",
  "aliases" : [ ],
  "summary" : "n8n-mcp affected by path traversal, redirect-following SSRF, and telemetry payload exposure",
  "details" : "## Impact\n\n`n8n-mcp` versions before 2.50.1 contained three independently-reported issues affecting deployments that run the n8n API integration:\n\n1. **Caller-supplied identifiers were not validated before being used as URL path segments** by the n8n API client. An authenticated MCP caller passing a crafted workflow id could cause outbound requests carrying the configured n8n API key to land on other same-origin endpoints, bypassing handler-level access controls (including `DISABLED_TOOLS`).\n\n2. **Validated webhook, form, and chat trigger URLs followed redirects.** A URL that passed initial validation could redirect the outbound request to a host that would otherwise have been rejected, with the response body returned to the caller. Reachable as non-blind SSRF over authenticated MCP calls.\n\n3. **Mutation telemetry stored unredacted operation payloads.** On instances running with the default opt-in telemetry, partial-update operation diffs were uploaded without redaction. Operation values can carry the same node-parameter values the workflow contains, including bearer tokens, API keys, and webhook secrets.\n\n## Severity\n\nCVSS 8.3 (HIGH). Exploitation requires an authenticated MCP caller and an n8n API integration configured with an n8n API key.\n\n## Patched versions\n\nUpgrade to `n8n-mcp >= 2.50.1`.\n\n## Workarounds\n\n- For issues (1) and (2): restrict network access to the HTTP transport (firewall, reverse-proxy ACL, or VPN) so only trusted callers can reach the MCP HTTP port; or switch to stdio mode, which exposes no HTTP surface for these issues.\n- For issue (3): set `N8N_MCP_TELEMETRY_DISABLED=true` in the environment before starting the server, or run `npx n8n-mcp telemetry disable` once.\n\n## Credit\n\nReported by @cybercraftsolutionsllc.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n-mcp"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.50.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/czlonkowski/n8n-mcp/security/advisories/GHSA-8g7g-hmwm-6rv2"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/czlonkowski/n8n-mcp/commit/1cfe9c6bddb4b1634e6e23323c18ea35fd196999"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/czlonkowski/n8n-mcp"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/czlonkowski/n8n-mcp/releases/tag/v2.50.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-22", "CWE-918" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-08T17:00:09Z",
    "nvd_published_at" : null
  }
}