CVE-2026-45582 n8n-MCP: Workflow telemetry sanitizer could retain partial values from URL-shaped node parameters
The n8n-MCP telemetry sanitizer fails to fully redact sensitive URL parameters, potentially leaking secrets to the telemetry backend.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-45582?
CVE-2026-45582 is a medium-severity vulnerability in czlonkowski n8n-mcp, published on 29 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
n8n-MCP is an MCP server that provides AI assistants access to n8n node documentation, properties, and operations. Prior to 2.51.3, 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. This vulnerability is fixed in 2.51.3.
Weakness: CWE-201
Which versions are affected by CVE-2026-45582?
2 open source packages ship an affected version, including n8n-mcp. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
n8n-mcp npm | All versions | 2.51.3 |
n8n-mcp npm | All versions | 2.51.3 |
Products include N8n-Mcp N8n-Mcp.
How do I fix CVE-2026-45582?
Upgrade n8n-mcp to 2.51.3 or later.
Is CVE-2026-45582 being exploited?
There is no known exploitation of CVE-2026-45582 in the wild and no public exploit code.
Other vulnerabilities in czlonkowski n8n-mcp
- CVE-2026-54052 n8n-MCP: Cross-tenant access to workflow version backups in multi-tenant HTTP deployments
- CVE-2026-42449 n8n-MCP: IPv4-mapped IPv6 addresses bypass SSRF protection in validateUrlSync(), enabling full SSRF for SDK embedders
- CVE-2026-39974 n8n-MCP has an Authenticated SSRF via instance-URL header in multi-tenant HTTP mode
- CVE-2026-45707 n8n-MCP: Multi-tenant MCP requests fall back to process-level n8n credentials when tenant headers are absent or incomplete
- CVE-2026-44694 n8n-MCP: Authenticated SSRF in n8n-mcp webhook and API client paths
Sources
Also known as GHSA-f3rg-xqjj-cj9w.