Skip to main content
VulnerabilityPublished Updated

n8n-mcp has unauthenticated session termination and information disclosure in HTTP transport

Affects n8n-mcpSource GCVE Database

0

CVSS 8.2 High : upgrade to 2.47.6 soon.

Data as of 9 Nov 2026, 19:34 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.47.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

What to do

Upgrade n8n-mcp to 2.47.6.

Affected software

ProductAffectedFixed in
Homebrewn8n-mcppkg:brew/n8n-mcpOther threatsAffected
  • >=2.14.1 <2.47.6
Fixed in
  • 2.47.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to n8n-mcp version 2.47.6 or later, where all MCP session endpoints require Bearer authentication and the health check endpoint is limited. If immediate upgrade is not possible, restrict network access to the HTTP server using firewall rules, reverse proxy IP allowlists, or VPNs to allow only trusted clients. Alternatively, use stdio mode (MCP_MODE=stdio) which does not expose HTTP endpoints and is not affected by this vulnerability.

Description

### Summary Several HTTP transport endpoints in n8n-mcp lacked proper authentication, and the health check endpoint exposed sensitive operational metadata without credentials. ### Impact An unauthenticated attacker with network access to the n8n-mcp HTTP server could disrupt active MCP sessions and gather information useful for further attacks. ### Patches 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. ### Workarounds 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. ### Credit Reported by @yotampe-pluto.

References

Community reviews

Loading reviews…