Mcp-Go (<= 1.2.1) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/mcp-go--1.2.1/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioSun, 11 Oct 2026 16:02:48 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgDenial of Service Vulnerability in mcp-gohttps://feed.craftedsignal.io/briefs/2026-10-mcp-go-dos/Sun, 11 Oct 2026 16:02:48 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-mcp-go-dos/mcp-go versions through 1.2.1 contain a denial of service vulnerability in StreamableHTTPServer.ServeHTTP that allows remote, unauthenticated attackers to trigger memory exhaustion via oversized POST request bodies.mcp-go versions through 1.2.1 are susceptible to a denial of service (DoS) vulnerability located within the StreamableHTTPServer.ServeHTTP function. The vulnerability is caused by an unsafe implementation where the server reads the entirety of an incoming POST request body into memory using the io.ReadAll function before any validation logic is executed. This design flaw allows remote, unauthenticated attackers to transmit either a single arbitrarily large POST body or multiple concurrent requests, rapidly consuming the available memory of the host process. Successful exploitation leads to memory exhaustion, causing the server process to crash or be terminated by the operating system's out-of-memory (OOM) killer. This impacts the availability of any service relying on the mcp-go library for handling HTTP streams.

Impact

Successful exploitation of this vulnerability results in a denial of service for the affected application. Because the impact is memory exhaustion, the entire service process may terminate, requiring manual intervention or automated restart procedures to recover. This affects any infrastructure or internal service components that have integrated mcp-go versions 1.2.1 or earlier for handling HTTP communication.

Recommendation

  • Upgrade the mcp-go library to a version later than 1.2.1 where request body validation occurs prior to buffering or where memory limits are enforced during read operations.
  • Implement request body size limits at the load balancer or reverse proxy layer (e.g., Nginx client_max_body_size) to prevent excessively large payloads from reaching the application server.
  • Audit custom HTTP server implementations using mcp-go to ensure that io.ReadAll is not used on unvalidated request streams.
]]>lowadvisory