CVE-2026-132121

Supergateway WebSocket mode could let a web page invoke local MCP tools

supercorp-ai · Supergateway stdio-to-WebSocket gateway

First documented disclosure · Review checkpoint

Summary

A malicious web page could connect to an unauthenticated local MCP gateway and use its tools.

Severity and exploitation evidence

High · 8.6/10 · CVSS 4.0. Severity source.

Exploitation not established: Malicious exploitation remains unverified in the reviewed sources.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The WebSocket upgrade path did not enforce an allowed browser origin.

Conditions required

The user visits attacker-controlled content while a reachable gateway runs without API-key protection.

Potential impact

Wrapped MCP tools can access files, execute commands or invoke services with the gateway user’s privileges, depending on the installed tools.

Affected versions and configurations

2.4.0 through 4.2.2, according to the CNA.

Fix and mitigation status

A corrected release remains unverified; the latest reviewed release is 4.2.2.

Practical next steps

Disable exposed WebSocket mode or require authenticated upgrades and enforce an explicit origin policy. Loopback binding alone does not prevent browser access.

Operating lesson

Authenticate WebSocket upgrades and enforce browser-origin boundaries for local agent services.

Evidence and limits

Original public disclosure 2026-11-17; CVE publication 2026-11-18. The reporter’s browser demonstrations establish the claimed mechanism. Public researcher GHSAs reside under a fork, not the upstream maintainer repository.

Sources