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:
Authorization headerx-n8n-key header in multi-tenant setupsAccess control itself was not bypassed — unauthenticated requests were correctly rejected with 401 Unauthorized — but sensitive values from those rejected requests could still be persisted in logs.
Impact category: CWE-532 (Insertion of Sensitive Information into Log File).
Deployments running n8n-mcp v2.47.10 or earlier in HTTP transport mode (MCP_MODE=http). The stdio transport is not affected.
v2.47.11 and later.
npx n8n-mcp@latest (or pin to >= 2.47.11)docker pull ghcr.io/czlonkowski/n8n-mcp:latestIf users cannot upgrade immediately:
MCP_MODE=stdio, the default for CLI invocation), which has no HTTP surface.n8n-MCP thanks @S4nso (Organization / Jormungandr) for reporting this issue.
{
"github_reviewed": true,
"github_reviewed_at": "2026-04-23T14:31:46Z",
"cwe_ids": [
"CWE-532"
],
"severity": "MODERATE",
"nvd_published_at": null
}