Vulnerability  ·  2026-11-19

Supergateway cross-site WebSocket hijacking lets a malicious page invoke an agent's MCP gateway (CVE-2026-132121)

VulnerabilityMedium impactGlobalCVE-2026-132121
Supergateway (an MCP stdio↔network bridge, 2.4.0 through 4.2.2) in stdio-to-WebSocket mode performs no Origin-header validation. A malicious web page can open /message over a WebSocket, including against localhost-bound gateways, and drive the bridged MCP server. The researcher's PoC (2026-11-17) exfiltrated a local file through the victim's gateway from four origins across 12/12 runs; the --apiKey option refuses unauthenticated upgrades. A second flaw (SGW-2026-001 / CVE-2026-131857) lets an unauthenticated attacker crash the gateway in stdio-to-SSE mode via prototype-inherited sessionId values.
Supergateway is commonly used to expose local MCP servers (which often hold the agent's file/API access) over WebSocket. Cross-site WebSocket hijacking lets a malicious web page the user visits connect to the local MCP gateway and invoke its tools — a zero-click from the agent's perspective, turning the agent's tool access into an attacker-controlled exfil/invoke channel. This is a browser-driven path into local AI coding-agent tooling.
A malicious web page opens a cross-site WebSocket to the victim's local MCP gateway (no Origin check) and invokes the bridged MCP server's tools / reads data, bypassing the agent's intended trust boundary.
Supergateway 2.4.0 through 4.2.2 (stdio-to-WebSocket mode)
Upgrade/patch Supergateway to validate Origin on the /message WebSocket, and enable --apiKey to refuse unauthenticated WebSocket upgrades.
Teycir supergateway-security-research (2026-11-17)NVD detail — CVE-2026-132121
See this in the live feed Explore related AI security and governance findings — updated every morning.
Open the feed →