UTC
Medium

n8n-MCP Logs Sensitive Request Data on Unauthorized /mcp Requests

CVE-2026-41495 · GHSA-pfm2-2mhg-8wpx · published 2026-04-23 · updated 2026-05-13

Severity
Medium
CVSS score
5.3
Chance of exploitation (EPSS)
0.26%
Fixed in
2.47.11
  • Exploitation No known exploitation
  • Automatable Yes
  • Technical impact Partial
  • CISA SSVC
What it is

When n8n-mcp runs in HTTP transport mode, incoming requests to the POST /mcp endpoint had their request metadata written to server logs regardless of the authentication outcome. In deployments where logs are collected, forwarded to external systems, or viewable outside the request trust boundary (shared log storage, SIEM pipelines, support/ops access), this can result in disclosure of: bearer tokens from the Authorization header per-tenant API keys from the x-n8n-key header in multi-tenant setups JSON-RPC request payloads sent to the MCP endpoint Access control itself was not bypassed — unauthenticated requests were correctly rejected with 401 Unauthorized — but sensitive values from those r…

What to do

Upgrade n8n-mcp to 2.47.11 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.11 and later. npm: npx n8n-mcp@latest (or pin to >= 2.47.11) Docker:

If you cannot upgrade yet

If users cannot upgrade immediately: Restrict network access to the HTTP port (firewall, reverse proxy, or VPN) so only trusted clients can reach the endpoint. Switch to stdio transport (MCP_MODE=stdio, the default for CLI invocation), which has no HTTP surface.

Affected
PackageRegistryAffectedFixed in
n8n-mcpnpm< 2.47.112.47.11

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].