Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

Low severity, with a CVSS score of 3.1, published 8 May 2026.

Which products and versions are affected?

n8n-mcp (npm) SEMVER:introduced=0,fixed=2.50.1.

Is there a fix for This vulnerability?

Yes. n8n-mcp (npm): upgrade to 2.50.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is This vulnerability attacked?

It is attacked over the network, in a software library.

Check whether you run n8n-mcp (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

n8n-mcp multiple vulnerabilities in API client and telemetry

Severity: low · CVSS 3.1 · Published 2026-05-08

n8n-mcp is a Node.js integration tool that connects n8n workflow automation with Model Context Protocol clients. Versions before 2.50.1 contain three distinct security flaws: unauthenticated path traversal allowing access to unintended API endpoints, redirect-following SSRF attacks against configured webhook and form URLs, and unredacted telemetry data containing sensitive credentials like API keys and webhook secrets. Exploitation requires authentication to the MCP interface and could expose sensitive workflow data or allow lateral movement within connected services.

Technologies: n8n-mcp (npm). Vendors: npm.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: Low severity, with a CVSS score of 3.1, published 8 May 2026.
Which products and versions are affected?: n8n-mcp (npm) SEMVER:introduced=0,fixed=2.50.1.
Is there a fix for This vulnerability?: Yes. n8n-mcp (npm): upgrade to 2.50.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked over the network, in a software library.
Am I affected?: Check whether you run n8n-mcp (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

n8n-mcp (npm): upgrade to 2.50.1 or later
```
npm install n8n-mcp@2.50.1
```

Technical details

The vulnerability consists of three independently reported issues: (1) Path traversal via unvalidated workflow identifiers used as URL path segments in the n8n API client, allowing authenticated callers to bypass access controls by crafting malicious workflow IDs; (2) SSRF through redirect-following in webhook, form, and chat trigger URL validation, where URLs passing initial validation can redirect to otherwise-rejected hosts with response bodies returned to the caller; (3) Information disclosure through telemetry mutation tracking that stores unredacted operation payloads containing node parameters such as bearer tokens, API keys, and webhook secrets. All three issues require an authenticated MCP caller and an n8n API integration configured with an API key. The fix is available in n8n-mcp version 2.50.1 and later.

Affected products

n8n n8n-mcp < 2.50.1

Timeline

2026-05-08: disclosed
2026-05-08: patched: Patched in version 2.50.1

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.