CVE-2026-132121: Supergateway's stdio-to-WebSocket mode lets any website drive your local MCP server's tools (2.4.0 through 4.2.2, no fix yet)
Supergateway (supercorp-ai) wraps stdio MCP servers so they can be reached over SSE, WebSocket or HTTP. In stdio-to-WebSocket mode, versions 2.4.0 through 4.2.2 never check the Origin header on the WebSocket upgrade, and authentication is off by default. A web page the victim opens can connect to the gateway, even one bound to localhost, start an MCP session and call the wrapped server's tools (filesystem, shell, APIs) with the victim's privileges. 4.2.2 (10 November 2026) is the latest npm release, and the maintainers' issue was still open on 19 November 2026.
What it is
CWE-1385 (missing origin validation in WebSockets). The upgrade handler in src/gateways/stdioToWs.ts accepts any origin, including Origin: null. The researcher (Teycir) reports 12 of 12 successful exfiltrations across four origins, including from a real Chromium browser.
The same report (issue #378, opened 17 November 2026) also describes a high-severity unauthenticated DoS in stdio-to-SSE mode: POST /message?sessionId=toString (or another prototype-chain key) crashes the whole gateway. No CVE for that one was in NVD at the time of writing.
The researcher published the advisories under a fork (GHSA-mw77-x7vj-mfcc for this bug) and a research repository with exploits and a suggested patch, and asked the maintainers to issue official advisories and a fix.
How to check
- Look for supergateway in your MCP client configs, scripts and Docker images, and check whether you start it with --outputTransport ws.
- Check the installed version; 2.4.0 through 4.2.2 are affected.
How to fix
- Until a patched release ships, don't run Supergateway in stdio-to-WebSocket mode on a machine where you browse the web. Use the stdio server directly, or SSE/Streamable HTTP behind a proxy that checks Origin and requires a token.
- If you must use WebSocket mode, put it behind a reverse proxy that rejects upgrades whose Origin isn't on an allowlist and requires an API key.
- Watch the Supergateway repository (issue #378) for a fixed version.
npm ls supergateway
npm ls -g supergateway
grep -rn "supergateway" ~/.cursor ~/.config ~/Library/Application\ Support/Claude 2>/dev/null | grep -i ws Sources
- criticalMalicious npm package @guicai777/mcp-doctor posed as an MCP diagnostic tool and dropped a hidden Windows executable, with a README telling users to run mshta (MAL-2026-20295)
- criticalCVE-2026-77359: Jupyter MCP Server's /api/connect and /api/stop routes skipped the token and Origin checks, so a website or network caller could repoint it to an attacker's Jupyter backend (fixed 1.0.3)
- criticalMalicious npm packages posing as AI SDKs and MCP servers: character-ai-sdk, char-ai-sdk, @mibbp/agent-observer, mrnima-openai-chatgpt-bot and @fdcasj_dfew/md-doc-mcp
- criticalCVE-2026-76807: Doist's official Todoist MCP HTTP server let any website use DNS rebinding to read, create and delete your Todoist data (fixed 10.3.3)