CVE-2026-45707: czlonkowski n8n-mcp improper access control in multi-tenant mode

CVE-2026-45707 · Severity: high · CVSS 8.1 · Published 2026-05-29

n8n-mcp is a server that allows AI assistants to interact with n8n automation workflows. In multi-tenant configurations, a security flaw allowed authenticated users to bypass their own environment and execute commands against the service provider's primary n8n instance. This could lead to the unauthorized viewing or modification of sensitive workflows, data tables, and credentials, potentially allowing an attacker to gain full control over the operator's automation environment.

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

Quick answers

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

Technical details

An improper access control vulnerability exists in n8n-mcp when configured with ENABLE_MULTI_TENANT=true. The application is designed to select the target n8n instance based on x-n8n-url and x-n8n-key headers provided in each request; however, if these headers are missing or incomplete, the system silently falls back to the process-level N8N_API_URL and N8N_API_KEY intended for the operator. An authenticated tenant can exploit this to execute management calls (reading/writing workflows, accessing data tables) against the operator's instance. In certain configurations, this could escalate to remote code execution if the operator's n8n instance permits Code-node execution. The vulnerability is fixed in version 2.51.2 by enforcing header presence and preventing credential fallback in multi-tenant mode.

Affected products

  • czlonkowski n8n-mcp <= 2.51.1

Identifiers

  • CVE-2026-45707
  • GHSA-jxx9-px88-pj69

Timeline

  • 2026-05-11: patched: Version 2.51.2 released
  • 2026-05-12: advisory: GitHub Security Advisory published
  • 2026-05-29: disclosed: CVE-2026-45707 published to NVD

References

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