Supergateway versions 4.2.0 through 4.2.2 contain a high-severity denial of service vulnerability that allows unauthenticated remote attackers to crash the gateway and terminate all attached MCP sessions.
Quick Take
- What: CVE-2026-131857, a denial of service flaw in Supergateway’s stdio-to-SSE mode that crashes the gateway via prototype-inherited sessionId values
- Who is affected: Users running Supergateway 4.2.0, 4.2.1, or 4.2.2 in stdio-to-SSE mode
- Severity: High (CVSS 7.5 base score, CVSS 8.7 v4.0)
- Status: Fix commit e2254169 referenced in the upstream repository; no fixed release number stated in the sources
- What to do: Apply the patch from commit e2254169a0780ec7c299fff7d51e128b013a65d3 or upgrade when a fixed release is announced
In plain English
Supergateway is a tool that bridges MCP (Model Context Protocol) servers to network connections. Researchers found that an attacker can crash the entire gateway by sending a single malicious web request with a special sessionId value like “toString” or “constructor”. No login or credentials are needed. When the gateway crashes, every user connected to it loses their session.
What you should do: If you use Supergateway 4.2.0, 4.2.1, or 4.2.2, you should apply the available patch. If you do not use Supergateway, you can ignore this issue.
What happened
On November 17, 2026, security researcher Teycir disclosed two high-severity vulnerabilities in Supergateway and published detailed research, exploits, and proof-of-concept code in a public GitHub repository. The first vulnerability, tracked as CVE-2026-131857 and designated SGW-2026-001 by the researcher, is a denial of service flaw in Supergateway’s stdio-to-SSE mode.
The vulnerability exists in versions 4.2.0 through 4.2.2. An unauthenticated attacker can send a POST request to the /message endpoint with a sessionId query parameter set to a prototype-inherited property name such as toString, __proto__, constructor, hasOwnProperty, or valueOf. The vulnerable code stores sessions in a plain JavaScript object without ownership checks. When the attacker supplies a prototype chain key, the code retrieves a truthy non-session value, which triggers an unhandled TypeError in an asynchronous Express handler. Node.js exits on the unhandled rejection, terminating the entire gateway process and every attached MCP session.
The researcher verified the vulnerability in 15 out of 15 crash attempts across five different payload values, including reproduction over a non-loopback network interface and via raw TCP using netcat. The researcher also demonstrated that a patched build returns a 503 error, remains running, and continues to serve legitimate sessions.
Teycir published GitHub Security Advisories GHSA-96g7-x7h4-cr9v (for CVE-2026-131857) and GHSA-mw77-x7vj-mfcc (for a second vulnerability, SGW-2026-002, a Cross-Site WebSocket Hijacking flaw) on November 17, 2026. Because the researcher’s GitHub token had only read access to the upstream supercorp-ai/supergateway repository, the advisories were published under the Teycir/supergateway fork. The researcher contacted the vendor via GitHub issue #378 on the same day and requested that canonical advisories be submitted under the correct repository and that CVE assignment be coordinated through the GitHub CNA.
VulnCheck published an advisory on November 17, 2026, assigning CVSS v4.0 score 8.7 (CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N). The NVD entry lists CVSS 7.5. The researcher’s repository includes a validated patch and states that the fix replaces the plain object with a Map and validates ownership. A commit (e2254169a0780ec7c299fff7d51e128b013a65d3) in the upstream repository is referenced in the sources, but the sources do not state a fixed version number or release.
What you should do
If you are running Supergateway 4.2.0, 4.2.1, or 4.2.2, apply the patch from commit e2254169a0780ec7c299fff7d51e128b013a65d3 or monitor the upstream repository for a fixed release. The researcher’s supergateway-security-research repository on GitHub contains the patch file and verification scripts. Until a fixed release is out, keep the gateway off public networks and restrict who can reach its message endpoint.
If you do not use Supergateway, no action is required.
What it means
This vulnerability demonstrates a classic prototype pollution variant: storing user-controlled keys in a plain JavaScript object without checking hasOwnProperty allows an attacker to retrieve inherited properties from the prototype chain. In this case, the result is not data corruption but a type error that crashes the entire process. The flaw is trivial to exploit, requires no authentication, and affects all users of the gateway simultaneously.
The researcher’s disclosure included a second high-severity vulnerability (SGW-2026-002, GHSA-mw77-x7vj-mfcc) affecting Supergateway’s WebSocket mode, which allows Cross-Site WebSocket Hijacking due to missing Origin validation. That vulnerability is tracked separately.
MCP gateways are a recurring target for denial of service bugs: recent cases include a tool name collision crash in IBM ContextForge and a ReDoS flaw in the same gateway. New cases are tracked in our AI Security hub.
Sources
- NVD CVE-2026-131857
- Teycir supergateway-security-research repository
- Vulnerable code in Supergateway 4.2.2
- Supergateway commit e2254169
- Supergateway issue #378
- VulnCheck advisory



