UTC
Medium

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
What it is

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.

What to do

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 you cannot upgrade yet

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.

Affected
PackageRegistryAffectedFixed in
n8n-mcpnpm< 2.47.132.47.13

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.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].