Answer in brief
CVE-2026-108395 records a High severity (CVSS 7.5) vulnerability in Model Context Protocol Java SDK HTTP server transports allow memory exhaustion through unbounded request bodies. The current sources do not mark it as known exploited. The current feed maps modelcontextprotocol/io.modelcontextprotocol.sdk:mcp (generic), modelcontextprotocol/io.modelcontextprotocol.sdk:mcp-core (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps modelcontextprotocol/io.modelcontextprotocol.sdk:mcp (generic), modelcontextprotocol/io.modelcontextprotocol.sdk:mcp-core (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| modelcontextprotocol/io.modelcontextprotocol.sdk:mcpgeneric | >=0.8.0 <0.13.0 | 0.13.0 |
| modelcontextprotocol/io.modelcontextprotocol.sdk:mcp-coregeneric | >=0.13.0 <0.18.4 || >=1.0.0 <1.1.4 || >=2.0.0-M1 <2.0.1 | 0.18.4, 1.1.4, 2.0.1 |
Published upstream
Oct 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 14, 2026
The Model Context Protocol Java SDK is the official Java SDK for Model Context Protocol servers and clients. From version 0.8.0 through 0.12.0 in the io.modelcontextprotocol.sdk:mcp artifact, from 0.13.0 through 0.18.3 and 1.0.0 through 1.1.3 in io.modelcontextprotocol.sdk:mcp-core, and from mcp-core 2.0.0-M1 through 2.0.0, the Servlet-based SSE, Streamable HTTP, and Stateless server transports read an HTTP request body into memory without enforcing a maximum size. An unauthenticated remote client able to reach an affected transport can stream an arbitrarily large POST body, including with chunked transfer encoding, until the Java process exhausts its heap and becomes unavailable. Authentication, Origin or Host validation, or an upstream request-size limit can reject the request before the vulnerable read. The maintained mcp-core lines are fixed in versions 0.18.4, 1.1.4, and 2.0.1.
Quoted source text, attributed separately from HOL analysis.