# Supergateway: a web page can drive the MCP gateway's tools

> Supergateway's WebSocket mode accepts connections from any web page, handing a visited site the tools of the MCP server behind it.

- **Severity:** Medium: Real and reproducible, but needs unusual setup, user help or a narrow audience. Plan a fix.
- **Category:** Vulnerability
- **Published by:** Teycir
- **Disclosed:** 2026-11-17
- **CVE:** CVE-2026-132121
- **CVSS:** 8.6
- **Affects:** Supergateway, supergateway (npm)
- **Research by:** [Teycir](https://github.com/Teycir)
- **Primary source:** https://github.com/Teycir/supergateway-security-research
- **Page:** https://theinjection.dev/items/supergateway-mcp-gateway-cswsh-dos/

Supergateway, the MCP stdio bridge, accepts WebSocket connections from any origin, so a web page a developer visits can invoke the wrapped server's tools. A second flaw ends every session from one unauthenticated request.

## What happened

Teycir published research on 17 November 2026 on two high-severity flaws in Supergateway, the bridge that exposes a stdio MCP server over SSE or WebSocket. VulnCheck assigned CVE-2026-132121 for the WebSocket flaw and CVE-2026-131857 for the denial of service. Both advisories reached NVD and the GitHub Advisory Database on 18 November.

## How it works

The WebSocket upgrade handler never checks the Origin header, so any page a victim visits can open the /message socket, even on a gateway bound to localhost. The attacker's script then initializes an MCP session and calls the wrapped server's tools with the victim's privileges. The separate denial of service sends a POST to /message with sessionId set to toString or constructor, which reaches an unhandled TypeError and terminates every attached session.

## Who is affected

Versions 2.4.0 through 4.2.2 carry the WebSocket hijacking, in stdio-to-WebSocket mode, and 4.2.0 through 4.2.2 carry the denial of service, in stdio-to-SSE mode. Developers who run the gateway on a workstation while browsing are the exposed group.

## What to do

Set an API key so the gateway refuses unauthenticated upgrades, and prefer the SSE bridge over the WebSocket transport where it will do. Both advisories list no fixed version, and the latest release, 4.2.2, predates the report.

## Quick facts

- **Affected:** Supergateway 2.4.0 to 4.2.2
- **CVE:** CVE-2026-132121 and CVE-2026-131857
- **CVSS:** 8.6 and 8.7, CVSS v4, per NVD
- **Fixed in:** No fixed release listed
- **Found by:** Teycir
- **Disclosed:** 17 November 2026

## Sources

1. [Research Write-Up](https://github.com/Teycir/supergateway-security-research)
2. [WebSocket Advisory](https://github.com/advisories/GHSA-cp8r-6jmm-c5qw)
3. [Denial Of Service](https://github.com/advisories/GHSA-vpvw-x889-f934)
4. [Upstream Issue](https://github.com/supercorp-ai/supergateway/issues/378)
