Allocation of Resources Without Limits or Throttling Affecting io.modelcontextprotocol.sdk:mcp-core package, versions [0.18.0, 0.18.4)[1.0.0, 1.1.4)[2.0.0,2.0.1)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JAVA-IOMODELCONTEXTPROTOCOLSDK-21717092
- published26 Oct 2026
- disclosed14 Oct 2026
- creditrazashariff, tonghuaroot, hewei-gikaku, mohammad228, Gal3m, shmulc8
Introduced: 14 Oct 2026
NewCVE-2026-108395 (opens in a new tab)How to fix?
Upgrade io.modelcontextprotocol.sdk:mcp-core to version 0.18.4, 1.1.4, 2.0.1 or higher.
Overview
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via unbounded request-body reads in its Servlet-based Streamable HTTP, Stateless, and SSE server transports. When exposed to untrusted network input without an upstream body-size limit, a remote client can send a POST with a streamed body, such as one using chunked transfer encoding, that the transport buffers entirely in memory. A single request can exhaust the server heap, starving or crashing the process.
Notes
- At the request-validation step, the POST must pass any configured Origin/Host allow-list and authentication checks; these can reject it before the transport reads the body.
Workarounds
- Configure the reverse proxy or gateway in front of the server to enforce a request-body size limit. This limits streamed or chunked requests before they can cause unbounded buffering in the affected HTTP transports.