Supergateway 2.4.0 through 4.2.2 Cross-Site WebSocket Hijacking via stdioToWs
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| supercorp-ai | supergateway | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Supercorp-ai | Supergateway |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Supercorp-ai
Supercorp-ai supergateway |
|
| Vendors & Products |
Supercorp-ai
Supercorp-ai supergateway |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Supergateway 2.4.0 through 4.2.2 Cross-Site WebSocket Hijacking via stdioToWs | |
| Weaknesses | CWE-1385 | |
| References |
|
|
| Metrics |
cvssV3_1
|
Missing Origin Validation in WebSockets