n8n-mcp has unauthenticated session termination and information disclosure in HTTP transport
GHSA-75hx-xj24-mqrw · published 2026-04-10
- Severity
- High
- CVSS score
- 8.2
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 2.47.6
An unauthenticated attacker with network access to the n8n-mcp HTTP server could disrupt active MCP sessions and gather information useful for further attacks.
Upgrade n8n-mcp to 2.47.6 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.
Fixed in v2.47.6. All MCP session endpoints now require Bearer authentication. The health check endpoint has been reduced to a minimal liveness response.
If you cannot upgrade immediately: Restrict network access to the HTTP server using firewall rules, reverse proxy IP allowlists, or a VPN so that only trusted clients can reach it. Use stdio mode (MCP_MODE=stdio) instead of HTTP mode. The stdio transport does not expose any HTTP endpoints and is unaffected by this vulnerability. Upgrading to v2.47.6 is still strongly recommended.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| n8n-mcp | npm | <= 2.47.5 | 2.47.6 |
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- Criticaln8n-MCP: Cross-tenant access to workflow version backups in multi-tenant HTTP deploymentsn8n-mcp
- Highn8n-MCP: Multi-tenant MCP requests fall back to process-level n8n credentials when tenant headers are absent or incompleten8n-mcp
- Highn8n-mcp affected by path traversal, redirect-following SSRF, and telemetry payload exposuren8n-mcp
- Highn8n-mcp webhook and API client paths has an authenticated SSRFn8n-mcp
- Highn8n-mcp's IPv4-mapped IPv6 addresses bypass SSRF protection in validateUrlSync(), enabling full SSRF for SDK embeddersn8n-mcp
- Highn8n-mcp has authenticated SSRF via instance-URL header in multi-tenant HTTP moden8n-mcp
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.