CVE-2026-132121
8.1HighPublished 18 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite
High
0CVSS v3.110
- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User action
- Required
- Impact
- High impact on confidentiality, integrity
- Weakness
- CWE-1385
What an attacker gets
Remote attackers can hijack WebSocket connections to execute arbitrary tools with the victim's privileges. This requires a user to visit a malicious website while the gateway is running.
Root cause
The application fails to validate the Origin header when establishing WebSocket connections in stdio-to-WebSocket mode.
Affected versions
Supergateway 2.4.0 through 4.2.2
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Fix & remediation
Upgrade to Supergateway 4.2.3 or later. If you cannot patch immediately, disable stdio-to-WebSocket mode in your configuration file.
$ npm install -g supergateway@latestAI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
Supergateway 2.4.0 through 4.2.2 contains a cross-site WebSocket hijacking vulnerability in stdio-to-WebSocket mode that allows malicious web pages to connect by bypassing missing Origin header validation. Attackers can open the /message WebSocket from a victim's browser, even against localhost-bound gateways, to initialize an MCP session and invoke wrapped stdio MCP server tools with victim privileges.
References
- https://github.com/Teycir/supergateway-security-research
- https://github.com/supercorp-ai/supergateway
- https://github.com/supercorp-ai/supergateway/blob/v4.2.2/src/gateways/stdioToWs.ts#L104-L126
- https://github.com/supercorp-ai/supergateway/issues/378
- https://www.vulncheck.com/advisories/supergateway-2.4.0-through-4.2.2-cross-site-websocket-hijacking-via-stdiotows