n8n-MCP: Sensitive MCP tool-call arguments logged on authenticated requests in HTTP mode
CVE-2026-42282 · GHSA-wg4g-395p-mqv3 · published 2026-04-25 · updated 2026-05-13
- Severity
- Medium
- CVSS score
- 4.3
- Chance of exploitation (EPSS)
- 0.25%
- Fixed in
- 2.47.13
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
When n8n-mcp runs in HTTP transport mode, authenticated MCP tools/call requests had their full arguments and JSON-RPC params written to server logs by the request dispatcher and several sibling code paths before any redaction. When a tool call carries credential material — most notably n8nmanagecredentials.data — the raw values can be persisted in logs.
Upgrade n8n-mcp to 2.47.13 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.
v2.47.13 and later. npm: npx n8n-mcp@latest (or pin to >= 2.47.13) Docker: The patch routes tool-call arguments through a metadata-only summarizer (summarizeToolCallArgs) that records type, top-level key names, and approximate size — never values. The same pattern was adopted earlier for HTTP request bodies in GHSA-pfm2-2mhg-8wpx.
If developers cannot upgrade immediately: Restrict access to the HTTP port (firewall, reverse proxy, or VPN) so only trusted clients can authenticate. Restrict access to server logs (no shared SIEM ingestion, no support read-only access) until the upgrade lands. Switch to stdio transport (MCP_MODE=stdio, the default for CLI invocation), which has no HTTP surface and short-circuits the affected log calls.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| n8n-mcp | npm | < 2.47.13 | 2.47.13 |
- 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.