n8n-MCP: Workflow telemetry sanitizer could retain partial values from URL-shaped node parameters
CVE-2026-45582 · GHSA-f3rg-xqjj-cj9w · published 2026-05-18 · updated 2026-06-09
- Severity
- Medium
- CVSS score
- 6.5
- Chance of exploitation (EPSS)
- 0.26%
- Fixed in
- 2.51.3
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
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.
Upgrade n8n-mcp to 2.51.3 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
Fixed in n8n-mcp 2.51.3. Upgrading is the recommended remediation.
For users who cannot upgrade immediately, disable anonymous telemetry by setting any of these environment variables to true: N8NMCPTELEMETRYDISABLED TELEMETRYDISABLED DISABLE_TELEMETRY
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| n8n-mcp | npm | < 2.51.3 | 2.51.3 |
- CriticalPhoenix: Format String Injection in applyChatTemplatearize-phoenix
- CriticalFlowise: Unauthenticated OAuth2 token refresh endpoint returns access tokens — enables token theft for any connected serviceflowise
- CriticalMLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltrationmlflow
- CriticalvLLM has RCE In Video Processingvllm
- HighConfig revision hashes could expose password verifiersopenclaw
- Highn8n: Shared Credential Header Leak via HTTP Request Pagination Expressionn8n, n8n, n8n
- Criticaln8n-MCP: Cross-tenant access to workflow version backups in multi-tenant HTTP deploymentsn8n-mcp
- Highn8n-MCP: Multi-tenant MCP requests fall back to process-level n8n credentials when tenant headers are absent or incompleten8n-mcp
- Highn8n-mcp affected by path traversal, redirect-following SSRF, and telemetry payload exposuren8n-mcp
- Highn8n-mcp webhook and API client paths has an authenticated SSRFn8n-mcp
- Highn8n-mcp's IPv4-mapped IPv6 addresses bypass SSRF protection in validateUrlSync(), enabling full SSRF for SDK embeddersn8n-mcp
- Highn8n-mcp has unauthenticated session termination and information disclosure in HTTP transportn8n-mcp
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.