# CVE-2026-132121: Supergateway 2.4.0 through 4.2.2 Cross-Site WebSocket Hijacking via stdioToWs


- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-cp8r-6jmm-c5qw

## What is CVE-2026-132121?

CVE-2026-132121 is a high-severity vulnerability in supercorp-ai supergateway, published on 18 Nov 2026. 

### Official 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.

Weakness: CWE-1385 (Missing Origin Validation in WebSockets)

## Which versions are affected by CVE-2026-132121?

1 open source package ship an affected version, including supergateway.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `supergateway` | npm | `pkg:npm/supergateway` | From 2.4.0 to 4.2.2 | None |

## How do I fix CVE-2026-132121?

No fix has been published for CVE-2026-132121 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-132121 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-132121 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-132121 and fix it if it is affected.

What it is: CVE-2026-132121 is a high-severity vulnerability in supercorp-ai supergateway, published on 18 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-132121 exists.

Affected packages and fixed versions:
- supergateway (npm): affected from 2.4.0 up to 4.2.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-132121/ (Markdown: https://insights.sbomify.com/CVE-2026-132121/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-132121
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-132121
- OSV: https://osv.dev/vulnerability/CVE-2026-132121

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-132121/
Summaries are generated and may contain mistakes; the official description above is the record.
