n8n-mcp
Affected
- introduced
0, fixed2.47.11(semver)
Fixed versions
2.47.11
Fix
- Fixed version
2.47.11npm install [email protected]
Advisory
Also known as: CVE-2026-41495
n8n-MCP Logs Sensitive Request Data on Unauthorized /mcp Requests
Impact
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).
Affected
Deployments running n8n-mcp v2.47.10 or earlier in HTTP transport mode (MCP_MODE=http). The stdio transport is not affected.
Patched
v2.47.11 and later.
npx n8n-mcp@latest (or pin to >= 2.47.11)docker pull ghcr.io/czlonkowski/n8n-mcp:latestWorkarounds
If users cannot upgrade immediately:
MCP_MODE=stdio, the default for CLI invocation), which has no HTTP surface.Credit
n8n-MCP thanks @S4nso (Organization / Jormungandr) for reporting this issue.
Medium Basis: The source's own band: MODERATE
0, fixed 2.47.11 (semver)2.47.11
2.47.11npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0