CVE-2026-44694: czlonkowski n8n-mcp authenticated SSRF in webhook and API client

CVE-2026-44694 · Severity: high · CVSS 4 · Published 2026-05-08

n8n-mcp is a server that allows AI assistants to interact with n8n automation workflows. A security flaw allows authenticated users or malicious AI prompts to force the server into making unauthorized network requests to internal systems. This could lead to the theft of sensitive cloud credentials or the exposure of private internal services, potentially compromising the entire cloud environment.

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

Quick answers

Is CVE-2026-44694 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-44694 being exploited in the wild.
How severe is CVE-2026-44694?
High severity, with a CVSS score of 4, published 8 May 2026.
Which products and versions are affected?
n8n-mcp (npm) >= 2.18.7, < 2.50.2, SEMVER:introduced=2.18.7,fixed=2.50.2.
Is there a fix for CVE-2026-44694?
Yes. n8n-mcp (npm): upgrade to 2.50.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44694 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-44694?
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.2 or later
    npm install n8n-mcp@2.50.2

Technical details

An authenticated Server-Side Request Forgery (SSRF) vulnerability exists in n8n-mcp affecting webhook trigger tools, the n8n API client, and per-request URLs in multi-tenant mode. The vulnerability stems from insufficient validation of URLs, allowing an attacker with MCP session access—or an attacker capable of influencing an LLM via indirect prompt injection—to bypass SSRF protections. This enables the attacker to make requests to internal RFC1918 networks and cloud metadata services (e.g., 169.254.169.254). Because the server returns the response body to the caller, it facilitates immediate exfiltration of IAM, GCP, or Azure managed-identity credentials. The issue is patched in version 2.50.2, which extends SSRF gating to the n8n API client base URL.

Affected products

  • czlonkowski n8n-mcp >= 2.18.7, < 2.50.2

Identifiers

  • CVE-2026-44694
  • GHSA-cmrh-wvq6-wm9r

Timeline

  • 2026-05-04: patched: Version 2.50.2 released
  • 2026-05-04: advisory: GitHub Security Advisory GHSA-cmrh-wvq6-wm9r published
  • 2026-05-08: disclosed: CVE-2026-44694 published to NVD

References

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