Advisory

GHSA-f3rg-xqjj-cj9w

Also known as: CVE-2026-45582

Summary

n8n-MCP: Workflow telemetry sanitizer could retain partial values from URL-shaped node parameters

Details

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_DISABLED
  • TELEMETRY_DISABLED
  • DISABLE_TELEMETRY

Credit

Reported by @u-ktdi.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-05-18 13:26 UTC
Modified
2026-06-09 10:45 UTC

Affected packages and fixes

n8n-mcp

npm · All systems

Affected

  • introduced 0, fixed 2.51.3 (semver)

Fixed versions

2.51.3

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences