# n8n-mcp missing authentication in HTTP transport

Source: https://junglewise.ai/threats/n8n-mcp-missing-authentication-in-http-transport-5b2c5068  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-10. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

Severity: low · CVSS 3.1 · Published 2026-04-10

n8n-mcp is a node.js library that provides Model Context Protocol (MCP) transport capabilities over HTTP and other protocols. Without proper authentication, an attacker can terminate active MCP sessions and extract sensitive operational metadata from the health check endpoint, disrupting service operations and gathering intelligence for further attacks.

Technologies: [n8n-mcp (npm)](https://junglewise.ai/threats/technologies/n8n-mcp). Vendors: [npm](https://junglewise.ai/threats/vendors/npm).

## Quick answers

**Is This vulnerability exploited in the wild?** No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

**How severe is This vulnerability?** Low severity, with a CVSS score of 3.1, published 10 April 2026.

**Which products and versions are affected?** n8n-mcp (npm) SEMVER:introduced=0,fixed=2.47.6.

**Is there a fix for This vulnerability?** Yes. n8n-mcp (npm): upgrade to 2.47.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is This vulnerability attacked?** It is attacked over the network.

**Am I affected?** Check whether you run n8n-mcp (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- n8n-mcp (npm): upgrade to 2.47.6 or later

  ```sh
  npm install n8n-mcp@2.47.6
  ```


## Technical details

The vulnerability stems from missing authentication (CWE-306) on several HTTP transport endpoints, particularly GET /mcp and DELETE /mcp routes, which relied on inconsistent secondary validation rather than explicit Bearer token authentication. The health check endpoint (GET /health) also exposed sensitive operational metadata including session statistics, memory usage, environment details, and token metadata without requiring credentials. An unauthenticated attacker with network access to the HTTP server can exploit this to terminate active MCP sessions via DELETE /mcp or gather operational information via GET /health. The fix, deployed in v2.47.6, adds mandatory Bearer authentication to all MCP session endpoints and trims the health endpoint to a minimal liveness response containing only status, version, uptime, and timestamp.

## Affected products

- n8n n8n-mcp < 2.47.6

## Timeline

- 2026-04-10: disclosed
- 2026-04-10: patched: Fixed in v2.47.6

## References

- [https://github.com/czlonkowski/n8n-mcp/security/advisories/GHSA-75hx-xj24-mqrw](https://github.com/czlonkowski/n8n-mcp/security/advisories/GHSA-75hx-xj24-mqrw)
- [https://github.com/czlonkowski/n8n-mcp/commit/ca9d4b3df6419b8338983be98f7940400f78bde3](https://github.com/czlonkowski/n8n-mcp/commit/ca9d4b3df6419b8338983be98f7940400f78bde3)

## Related threats

- [czlonkowski n8n-mcp incorrect authorization in multi-tenant HTTP mode](https://junglewise.ai/threats/cve-2026-55608-czlonkowski-n8n-mcp-incorrect-authorization-in-multi-tenant-http)
- [czlonkowski n8n-mcp authorization bypass in workflow backups](https://junglewise.ai/threats/cve-2026-54052-czlonkowski-n8n-mcp-authorization-bypass-in-workflow-backups)
- [czlonkowski n8n-mcp improper access control in multi-tenant mode](https://junglewise.ai/threats/cve-2026-45707-czlonkowski-n8n-mcp-improper-access-control-in-multi-tenant-mode)
- [czlonkowski n8n-mcp sensitive information leak in workflow telemetry](https://junglewise.ai/threats/cve-2026-45582-czlonkowski-n8n-mcp-sensitive-information-leak-in-workflow)
- [czlonkowski n8n-mcp authenticated SSRF in webhook and API client](https://junglewise.ai/threats/cve-2026-44694-czlonkowski-n8n-mcp-ssrf-in-webhook-and-api-client-paths)