Menu

The first of its kind: how one unbounded request body became a denial-of-service class across every major MCP SDK
📰

The first of its kind: how one unbounded request body became a denial-of-service class across every major MCP SDK

DEV Community: devsecops·razashariff·12 days ago
#OhMsWZPy
#devtodevsecops#devto#dev#server#body
Reading 0:00
15s threshold

The one-line version

In April 2026 I reported CVE-2026-39313 , a denial-of-service flaw in an MCP server framework. It was the first CVE of its kind: an unbounded HTTP request body, CWE-770, that lets a single unauthenticated request exhaust a Model Context Protocol server's memory and take it offline.

Over the next six months the identical flaw was found and patched in at least nine more MCP projects, including the official Python, Java, Go, Ruby, PHP and TypeScript SDKs . A third-party analysis in July called it "a new vulnerability category." By October two of those CVEs sat in the SDKs that the whole ecosystem is built on, together serving close to half a billion downloads a month.

This is the story of that class: how far it spread, who patched and who is still exposed, and why the two worst ones are effectively invisible to the scanners most teams rely on.

Every claim below links to a primary source.

What the bug actually is

MCP servers speak over an HTTP transport: Streamable HTTP, Server-Sent…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.