CVE-2026-131857
7.5HighPublished 18 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite
High
0CVSS v3.110
- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User action
- None
- Impact
- High impact on availability
- Weakness
- CWE-754
What an attacker gets
Unauthenticated attackers can crash the Supergateway and terminate all active MCP sessions. They only need to send a POST request with a crafted sessionId value.
Root cause
The application fails to validate the sessionId input, allowing prototype-inherited properties like toString or constructor to trigger an unhandled TypeError.
Affected versions
Supergateway 4.2.0 through 4.2.2
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Fix & remediation
Upgrade to version 4.2.3 or later. If you cannot patch immediately, block POST requests containing sessionId values of 'toString' or 'constructor' at your WAF or ingress controller.
$ npm install supergateway@latestAI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD 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.
References
- https://github.com/Teycir/supergateway-security-research
- 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://github.com/supercorp-ai/supergateway/issues/378
- https://www.vulncheck.com/advisories/supergateway-4.2.0-through-4.2.2-dos-via-prototype-inherited-sessionid