CVE-2026-45582

In affected versions of n8n-mcp, the workflow telemetry sanitizer could retain partial fragments of URL-shaped node parameters before sending workflow data to the project's anonymous telemetry backend. Values placed in HTTP-Request-style node parameters, such as customer or tenant identifiers, short secrets embedded in query strings, and signed request parameters, could therefore appear in stored telemetry, contrary to the collection boundary documented in PRIVACY.md.

Workarounds

For users who cannot upgrade immediately, disable anonymous telemetry by setting any of these environment variables to true:

• N8N_MCP_TELEMETRY_DISABLED
• TELEMETRY_DISABLED
• DISABLE_TELEMETRY

Credit

Reported by @u-ktdi.

Operators with access to the project's telemetry backend could read partial fragments of workflow URL parameters that should not have been collected. The bug was scoped to URL-shaped fields in workflow definitions; credentials, OAuth tokens, and workflow execution data are not affected, credentials are removed by a separate code path, and long secrets and known-provider tokens are matched by dedicated patterns.

CVE-2026-45582 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.51.3); upgrading removes the vulnerable code path.

Kodem intelligence

Fixed in n8n-mcp 2.51.3. Upgrading is the recommended remediation.

1. What is CVE-2026-45582? CVE-2026-45582 is a medium-severity security vulnerability in n8n-mcp (npm), affecting versions < 2.51.3. It is fixed in 2.51.3.
2. How severe is CVE-2026-45582? CVE-2026-45582 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of n8n-mcp are affected by CVE-2026-45582? n8n-mcp (npm) versions < 2.51.3 is affected.
4. Is there a fix for CVE-2026-45582? Yes. CVE-2026-45582 is fixed in 2.51.3. Upgrade to this version or later.
5. Is CVE-2026-45582 exploitable, and should I be worried? Whether CVE-2026-45582 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-45582 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-45582? Upgrade n8n-mcp to 2.51.3 or later.