CVE-2026-45582: n8n-MCP: Workflow telemetry sanitizer could retain partial values from URL-shaped node parameters
n8n-mcp before 2.51.3 sends workflow data to its anonymous telemetry backend after a sanitizer that only replaced the hostname of URL fields. Paths and query strings survived, so customer IDs, short secrets in query strings and signed parameters could be stored in telemetry. Upgrade to 2.51.3, or disable telemetry with an environment variable.
Published May 18, 2026 · Updated Jun 9, 2026 · Analysis Oct 27, 2026
What an attacker can do
n8n-mcp collects anonymous telemetry about the workflows it handles. The sanitizer in src/telemetry/workflow-sanitizer.ts treated url, endpoint and webhook fields by replacing only the hostname with [domain]. Everything after the host stayed in the data: the path and the query string. HTTP-Request-style node parameters often carry tenant or customer identifiers, short secrets and signed request parameters there.
This went against the collection boundary documented in PRIVACY.md. The exposure is to whoever can read the project's telemetry backend. No attacker action on your side is needed, so the CVSS vector (network, low privileges, high confidentiality) describes access to stored telemetry rather than an attack on your server.
The advisory limits the scope. Only URL-shaped fields in workflow definitions were affected. Credentials are removed by a separate code path. OAuth tokens and workflow execution data are not affected, and long secrets and known provider tokens are caught by dedicated patterns. Treat it as a privacy leak. It matters most if your workflows put short tokens or identifiers into URLs.
Who is affected
npm package n8n-mcp below 2.51.3, with telemetry enabled (the default unless you disabled it). Check the version and the settings:
npm ls -g n8n-mcp
env | grep -i telemetryFor Docker, check the image tag and container environment. If N8N_MCP_TELEMETRY_DISABLED, TELEMETRY_DISABLED or DISABLE_TELEMETRY is set to true, nothing was sent.
n8n-mcp
- Ecosystem
- npm
- Affected
- < 2.51.3
- Fixed in
- 2.51.3
- Check
npm ls n8n-mcp
How to fix it
Upgrade to n8n-mcp 2.51.3. The fix in pull request 782 makes sanitizeObject replace the whole value of any url, endpoint or webhook field with [REDACTED_URL], in both the workflow telemetry path and the mutation path. It also makes the event validator use a strict per-node schema with a limit of 1000 nodes, so unknown node keys are rejected before upload.
Workaround if you cannot upgrade: set N8N_MCP_TELEMETRY_DISABLED, TELEMETRY_DISABLED or DISABLE_TELEMETRY to true. Telemetry that was already sent cannot be recalled by you. If short tokens or signed URLs were in workflow URLs, rotate them.
How to tell if you were hit
Review your workflow definitions for URL, endpoint and webhook fields whose paths or query strings contain identifiers, tokens or signatures. Those are the values that could have been uploaded by affected versions. Check the version history of the n8n-mcp installs that handled those workflows and whether telemetry was enabled. Outbound traffic from the n8n-mcp process to the telemetry backend is the transport. The sources give no log signature for it.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
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.
Impact
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.
Patches
Fixed in n8n-mcp `2.51.3`. Upgrading is the recommended remediation.
Workarounds
For users who cannot upgrade immediately, disable anonymous telemetry by setting any of these environment variables to true:
N8N_MCP_TELEMETRY_DISABLEDTELEMETRY_DISABLEDDISABLE_TELEMETRY
Credit
Reported by @u-ktdi.
Credited to u-ktdi.
Questions
- Were my n8n credentials sent in telemetry?
The advisory says no. Credentials are removed by a separate code path, and OAuth tokens and workflow execution data are not affected. The leak concerned URL-shaped fields in workflow definitions.
- How do I stop the telemetry without upgrading?
Set N8N_MCP_TELEMETRY_DISABLED, TELEMETRY_DISABLED or DISABLE_TELEMETRY to true.
- Which version fixes CVE-2026-45582?
n8n-mcp 2.51.3. URL fields are now redacted whole to [REDACTED_URL] instead of just the hostname.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More Other MCP servers and tools vulnerabilities
All Other MCP servers and tools entriesCVE-2026-102943
Dagu MCP DAG specification read bypasses path containment and workspace isolation
medium6.5Nov 10, 2026CVE-2026-102610
fast-agent: `fast-agent serve` binds HTTP to 0.0.0.0 with no authentication by default; with --shell this is unauthenticated remote command execution
medium6.4Nov 9, 2026CVE-2026-63655
tsParticles: Unbounded HTTP Request Body Buffering in @tsparticles/mcp-server Leads to Remote DoS
high7.5Nov 9, 2026CVE-2026-76892
tsParticles: Malformed JSON requests can terminate the @tsparticles/mcp-server HTTP process
high8.7Nov 9, 2026CVE-2026-76893
tsParticles: A single anonymous MCP session can monopolize HTTP mode and deny new clients
medium6.9Nov 9, 2026CVE-2026-77604
Code Graph RAG: MCP paginated read_file path traversal / arbitrary file read
high7.5Nov 9, 2026
