Skip to main content
Menu
CVEs

CVE

Supergateway cross-site websocket hijacking in stdio-to-WebSocket mode

CVE-2026-132121EUVD-2026-128624Published Updated

8.6HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Supergateway 2.4.0 through 4.2.2 running in stdio-to-WebSocket mode

Summary

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.

Who should check

Teams running supercorp-ai supergateway 2.4.0 through 4.2.2 in stdio-to-WebSocket mode, including gateways bound to localhost.

“Supergateway 2.4.0 through 4.2.2 contains a cross-site WebSocket hijacking vulnerability in stdio-to-WebSocket mode”

vulncheck.com

cve.now Index

38Pcve.now Index 38 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach12/20supergateway: 106K downloads a week
  • Severity8.6/10CVSS 8.6
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 88 if added to CISA KEV
  • Would score about 83 if CISA's SSVC rates exploitation active

Impact

  • Widely used

    supergateway has 106k weekly downloads.Source: npmjs.com

    2 packages depend on supergateway.Source: deps.dev

What to do

  • Check whether your setup matches what the bug needs.

    Supergateway 2.4.0 through 4.2.2 running in stdio-to-WebSocket mode
  • Workaround: No fix is listed in the checked facts. Until one is available, limit exposure by not running Supergateway in stdio-to-WebSocket mode where a browser could reach it, if the setup allows that.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-132121 (Supergateway 2.4.0 through 4.2.2 Cross-Site WebSocket Hijacking via stdioToWs), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-132121 (entry last updated 2026-11-18):
Affected:
- npm package supergateway: from 2.4.0, through 4.2.2
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Supergateway 2.4.0 through 4.2.2 running in stdio-to-WebSocket mode (source: https://www.vulncheck.com/advisories/supergateway-2.4.0-through-4.2.2-cross-site-websocket-hijacking-via-stdiotows)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-132121 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132121 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/supercorp-ai/supergateway/issues/378
- https://github.com/supercorp-ai/supergateway/blob/v4.2.2/src/gateways/stdioToWs.ts#L104-L126
- https://github.com/supercorp-ai/supergateway
- https://www.vulncheck.com/advisories/supergateway-2.4.0-through-4.2.2-cross-site-websocket-hijacking-via-stdiotows
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-132121
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132121"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • From 2.4.0 · through 4.2.2

    No fix released. The latest release, 4.2.2, is still affected.

Evidence 7

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-132121

Is CVE-2026-132121 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

In stdio-to-WebSocket mode, a web page open in a victim's browser can connect to Supergateway's /message WebSocket and start an MCP session. From there it can call the tools of the wrapped stdio MCP server with the victim's privileges.Source: vulncheck.com

Which versions are affected by CVE-2026-132121?

supergateway (npm): from 2.4.0 through 4.2.2.Source: cve.now feed data

Am I affected, and how do I check?

Supergateway versions 2.4.0 through 4.2.2 running in stdio-to-WebSocket mode are affected. To check a setup, look at the installed Supergateway version and confirm whether it runs in stdio-to-WebSocket mode.Source: vulncheck.com

How do I fix CVE-2026-132121?

No fixed version is listed in the checked facts, so no upgrade target can be named from them. Check the vendor's advisory for patch information.Source: vulncheck.com

What if there's no patch?

No fix is listed in the checked facts. Until one is available, limit exposure by not running Supergateway in stdio-to-WebSocket mode where a browser could reach it, if the setup allows that.Source: vulncheck.com

More CVEs