CVE-2026-41495

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.

• npm: npx n8n-mcp@latest (or pin to >= 2.47.11)
• Docker: docker pull ghcr.io/czlonkowski/n8n-mcp:latest

Workarounds

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.

Credit

n8n-MCP thanks @S4nso (Organization / Jormungandr) for reporting this issue.

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 rejected requests could still be persisted in logs.

Impact category: CWE-532 (Insertion of Sensitive Information into Log File).

CVE-2026-41495 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.47.11); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-41495? CVE-2026-41495 is a medium-severity security vulnerability in n8n-mcp (npm), affecting versions < 2.47.11. It is fixed in 2.47.11.
2. How severe is CVE-2026-41495? CVE-2026-41495 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of n8n-mcp are affected by CVE-2026-41495? n8n-mcp (npm) versions < 2.47.11 is affected.
4. Is there a fix for CVE-2026-41495? Yes. CVE-2026-41495 is fixed in 2.47.11. Upgrade to this version or later.
5. Is CVE-2026-41495 exploitable, and should I be worried? Whether CVE-2026-41495 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-41495 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-41495? Upgrade n8n-mcp to 2.47.11 or later.