# GHSA-75hx-xj24-mqrw: n8n-mcp has unauthenticated session termination and information disclosure in HTTP transport

> Unauthenticated attackers can terminate active sessions and access sensitive metadata via HTTP endpoints in the n8n MCP server.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Apr 2026

## What is GHSA-75hx-xj24-mqrw?

GHSA-75hx-xj24-mqrw is a missing authorization vulnerability in n8n-mcp, published on 10 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

## Which versions are affected by GHSA-75hx-xj24-mqrw?

2 open source packages ship an affected version, including n8n-mcp.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `n8n-mcp` | npm | All versions | 2.47.6 |
| `n8n-mcp` | npm | All versions | 2.47.6 |

## How do I fix GHSA-75hx-xj24-mqrw?

Upgrade n8n-mcp to 2.47.6 or later.

## Is GHSA-75hx-xj24-mqrw being exploited?

There is no known exploitation of GHSA-75hx-xj24-mqrw in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-75hx-xj24-mqrw and fix it if it is affected.

What it is: GHSA-75hx-xj24-mqrw is a missing authorization vulnerability in n8n-mcp, published on 10 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-75hx-xj24-mqrw in the wild and no public exploit code.

Affected packages and fixed versions:
- n8n-mcp (npm): affected all versions; fixed in 2.47.6
- n8n-mcp (npm): affected all versions; fixed in 2.47.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-75hx-xj24-mqrw/ (Markdown: https://insights.sbomify.com/GHSA-75hx-xj24-mqrw/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-75hx-xj24-mqrw

---
From sbomify Insights: https://insights.sbomify.com/GHSA-75hx-xj24-mqrw/
Summaries are generated and may contain mistakes; the official description above is the record.