GHSA-75hx-xj24-mqrw is a high-severity (CVSS 8.2) vulnerability in n8n-mcp. A fix is available for n8n-mcp — see the affected versions and patch details below.
n8n-mcp has unauthenticated session termination and information disclosure in HTTP transport
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
n8n-mcpnpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | n8n-mcp | all versions | 2.47.6npm install n8n-mcp@2.47.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n-mcp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update n8n-mcp to 2.47.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-75hx-xj24-mqrw is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-75hx-xj24-mqrw can be triaged on real exposure rather than presence alone.
Tailored to GHSA-75hx-xj24-mqrw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-75hx-xj24-mqrw in your dependencies?
O3 Security finds GHSA-75hx-xj24-mqrw across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.